Triple
T10440926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Godspeed |
E246164
|
entity |
| Predicate | passengerComplement |
P881
|
FINISHED |
| Object | approximately 39 settlers |
—
|
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: approximately 39 settlers | Statement: [Godspeed, passengerComplement, approximately 39 settlers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengerComplement Context triple: [Godspeed, passengerComplement, approximately 39 settlers]
-
A.
passengers
chosen
Indicates that one entity is traveling in or being transported by another entity, typically as a non-operating occupant.
-
B.
hasPassengerServicesTo
Indicates that a transportation provider operates passenger services connecting one location or entity to another.
-
C.
majorPassengerService
Indicates that a transportation facility or route provides primary or significant passenger service as one of its main functions.
-
D.
transportIncludes
Indicates that a broader transport operation or service encompasses, contains, or makes use of a specific transport segment, mode, or component as part of its overall movement.
-
E.
airGroupComplement
Indicates that one air group serves as a complement or supporting component to another air group within a larger operational structure.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe083cd881909d2d8ad75d1d94cb |
completed | April 7, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69d4fb73a5e48190a8df4775bc5da80f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:15 p.m.