Triple
T3219069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phénix |
E67464
|
entity |
| Predicate | hasRefuelingSystem |
P21784
|
FINISHED |
| Object | hose‑and‑drogue system |
—
|
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: hose‑and‑drogue system | Statement: [Phénix, hasRefuelingSystem, hose‑and‑drogue system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRefuelingSystem Context triple: [Phénix, hasRefuelingSystem, hose‑and‑drogue system]
-
A.
hasRefuellingCapabilityFor
Indicates that one entity is capable of providing or performing refuelling operations for another entity.
-
B.
fuelSystem
Indicates a relationship where one entity serves as the fuel system (or part of it) that supplies, stores, or manages fuel for the operation of another entity.
-
C.
hasCentralTank
Indicates that an entity possesses or is equipped with a primary central tank as a key component or feature.
-
D.
hasOnboardSystems
chosen
Indicates that an entity is equipped with or contains specific onboard systems or subsystems.
-
E.
usedExternalTank
Indicates that an entity made use of an external tank as part of its operation or activity.
- 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_69ad858b8adc8190ad989712c87a476b |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adab0ef2c88190ab89e3217438a2bf |
completed | March 8, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0bb6c48190a0659c67d40ee37c |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:08 p.m.