Triple
T16335731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spirit |
E396673
|
entity |
| Predicate | firstSignalReceivedDate |
P122993
|
FINISHED |
| Object | 2004-01-04 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 2004-01-04 | Statement: [Spirit, firstSignalReceivedDate, 2004-01-04]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSignalReceivedDate Context triple: [Spirit, firstSignalReceivedDate, 2004-01-04]
-
A.
firstReachedDate
Indicates the date on which a particular entity first achieved, accessed, or arrived at a specified state, location, or milestone.
-
B.
firstInvocationDate
Indicates the date on which the entity was first invoked, used, or called for the first time.
-
C.
firstTakenAt
Indicates the time or date at which something was initially taken, captured, or recorded for the first time.
-
D.
firstUsedAt
Indicates the time or place at which something was initially used or put into operation.
-
E.
firstIntroductionDate
Indicates the date on which an entity was first introduced or presented for the first time.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4e3af7881908a3116c41ed69115 |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:07 a.m.