Triple
T22976998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aurora Lane |
E571349
|
entity |
| Predicate | travelStatus |
P100605
|
FINISHED |
| Object | passenger on a colony ship |
—
|
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: passenger on a colony ship | Statement: [Aurora Lane, travelStatus, passenger on a colony ship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelStatus Context triple: [Aurora Lane, travelStatus, passenger on a colony ship]
-
A.
IATAStatus
Indicates the current operational or membership status of an entity with respect to the International Air Transport Association (IATA).
-
B.
tourStatus
Indicates the current state or phase of a tour within its overall lifecycle (e.g., planned, active, completed, or canceled).
-
C.
fareStatus
Indicates the current condition or classification of a fare within a pricing or ticketing context (e.g., available, restricted, or expired).
-
D.
traveledAs
chosen
Indicates that an entity moved from one place to another in the role, capacity, or identity specified by another entity (e.g., as a tourist, as a representative, as a refugee).
-
E.
landerStatus
Indicates the current operational or situational state of a lander in its mission lifecycle.
- 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182369b548190a6630655a6e0bb39 |
completed | April 29, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:48 p.m.