Triple
T21130489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition 14 |
E520670
|
entity |
| Predicate | returnDateSTS-117 |
P112129
|
FINISHED |
| Object | 2007-06-22 |
—
|
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: 2007-06-22 | Statement: [Expedition 14, returnDateSTS-117, 2007-06-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnDateSTS-117 Context triple: [Expedition 14, returnDateSTS-117, 2007-06-22]
-
A.
dateOfReturnAsResidence
Indicates the date on which an entity returned to a particular place to resume or establish it as their residence.
-
B.
timeOfReturn
chosen
Indicates the specific time at which an entity comes back to a prior location or state.
-
C.
wasReturnedIn
Indicates that an item previously taken or sent was brought or sent back to its original source or owner at a specific time or in a specific context.
-
D.
wasReturnedTo
Indicates that an entity was sent or brought back to a previous owner, location, or state after having been away or removed.
-
E.
returnsAsGuestIn
Indicates that an entity comes back to participate or appear again in a context, but specifically in the role or capacity of a guest rather than a regular or primary member.
- F. None of above.
Provenance (3 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723556ec08190a2ade96c76f9cec7 |
completed | April 21, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:56 p.m.