Triple
T19474133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Endurance Crater |
E487198
|
entity |
| Predicate | entryDateByOpportunity |
P136060
|
FINISHED |
| Object | 2004-06-08 |
—
|
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-06-08 | Statement: [Endurance Crater, entryDateByOpportunity, 2004-06-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entryDateByOpportunity Context triple: [Endurance Crater, entryDateByOpportunity, 2004-06-08]
-
A.
entryDate
Indicates the date on which an entity was first recorded, created, or entered into a system or context.
-
B.
associatedWorkDate
Indicates the date on which a related or associated work (such as a publication, performance, or creation) is linked to the subject entity.
-
C.
referralDate
Indicates the date on which a referral from one party to another was made or formally recorded.
-
D.
engagementDate
Indicates the date on which two entities formally become engaged or committed to a relationship or agreement.
-
E.
officeCreatedInPeriod
Indicates that an office was created during a specified time period.
- 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633ef69508190b0d71ef663ba8977 |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004d3a708190a1c13c8f644f3926 |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:39 p.m.