Triple
T15536104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wei Tang triplets |
E370349
|
entity |
| Predicate | usesPilotingSystem |
P35891
|
FINISHED |
| Object | three-pilot drift |
—
|
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: three-pilot drift | Statement: [Wei Tang triplets, usesPilotingSystem, three-pilot drift]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPilotingSystem Context triple: [Wei Tang triplets, usesPilotingSystem, three-pilot drift]
-
A.
isDriverless
Indicates that something operates or moves without a human driver controlling it.
-
B.
hasDriverAssistance
Indicates that an entity is equipped with or supports driver assistance features or systems.
-
C.
hasNavigationTechnology
chosen
Indicates that an entity is equipped with or utilizes a system or technology for determining or guiding its position, route, or movement.
-
D.
requiresControlSystem
Indicates that one entity depends on or mandates the presence of a control system associated with another entity in order to function or be valid.
-
E.
hasPilotage
Indicates a relationship where one entity provides or is subject to navigational guidance or piloting services by another entity.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0442e327c8190b4b879c8a3cd38e3 |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:06 a.m.