Triple
T24084088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea-Based X-Band Radar |
E596585
|
entity |
| Predicate | crewAccommodation |
P74274
|
FINISHED |
| Object | habitable platform |
—
|
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: habitable platform | Statement: [Sea-Based X-Band Radar, crewAccommodation, habitable platform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewAccommodation Context triple: [Sea-Based X-Band Radar, crewAccommodation, habitable platform]
-
A.
crewCab
Indicates that a vehicle has a crew cab configuration, meaning its cabin is designed to seat multiple occupants in both front and rear rows.
-
B.
hasCrewQuarters
chosen
Indicates that one entity provides or contains designated living or sleeping quarters for the crew associated with it.
-
C.
crewOnboard
Indicates that a person or group is serving as crew aboard a specific vehicle, vessel, or craft.
-
D.
crewMate
Indicates that two entities are members of the same crew or team, sharing a common group affiliation or working together in a joint capacity.
-
E.
crewSystem
Indicates a relationship where a system is specifically designed for, assigned to, or operated by a particular crew.
- 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_69e288c4638c81909bacc28a1e3d436b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dc279ac48190b60a0753981f0b97 |
completed | April 29, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 10:44 p.m.