Triple
T8673482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cosmic Girl |
E205856
|
entity |
| Predicate | airlineConfigurationOrigin |
P84007
|
FINISHED |
| Object | passenger airliner |
—
|
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: passenger airliner | Statement: [Cosmic Girl, airlineConfigurationOrigin, passenger airliner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airlineConfigurationOrigin Context triple: [Cosmic Girl, airlineConfigurationOrigin, passenger airliner]
-
A.
typicalOriginAirportIATA
Indicates the usual or primary origin airport for an entity, identified by its IATA airport code.
-
B.
originatingFlight
Indicates that one entity is the original or initial flight from which another flight, journey, or related record derives or is associated.
-
C.
usedAircraftOrigin
Indicates the place or source from which a used aircraft was originally obtained or came.
-
D.
airlineType
Indicates the classification or category of an airline based on its operational or service characteristics.
-
E.
associatedAirlineHeadquarters
Indicates that an airline is connected to or based at a particular headquarters location.
- 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_69ca83529a9c8190b5c075b4f14636ed |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc491b807c81909563a34a947bc21a |
completed | March 31, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cc4564e018819081036722f3e42a71 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:31 p.m.