Triple
T37750603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gateway outpost |
E940970
|
entity |
| Predicate | hasCrewCapacityType |
P194400
|
FINISHED |
| Object | visiting crew only |
—
|
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: visiting crew only | Statement: [Gateway outpost, hasCrewCapacityType, visiting crew only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrewCapacityType Context triple: [Gateway outpost, hasCrewCapacityType, visiting crew only]
-
A.
hasCrewCapacity
Indicates that an entity is capable of accommodating a specified number of crew members.
-
B.
hasCrewedComponent
Indicates that an entity includes or is associated with a component that is operated or occupied by a crew.
-
C.
crewAndPassengersCount
Indicates the total number of people on a vehicle or vessel, combining both crew members and passengers.
-
D.
hasCrewFeature
Indicates that a crew possesses or is characterized by a particular feature, attribute, or capability.
-
E.
hasCrewCharacteristic
Indicates that a crew possesses a specified attribute, quality, or defining feature.
- 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_69f76ee1f3a88190834e6c8af99bccc9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
| PDg | Predicate description generation | batch_69fd6dbc3ac0819093fbcfe95f12b93d |
completed | May 8, 2026, 4:59 a.m. |
Created at: May 3, 2026, 4:19 p.m.