Triple
T35639229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COMAC |
E1029811
|
entity |
| Predicate | ARJ21Role |
P175697
|
FINISHED |
| Object | regional jetliner |
—
|
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: regional jetliner | Statement: [COMAC, ARJ21Role, regional jetliner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ARJ21Role Context triple: [COMAC, ARJ21Role, regional jetliner]
-
A.
referredAircraftRole
Indicates that one aircraft is mentioned or designated in relation to another aircraft’s role, function, or status within a specific context or event.
-
B.
testAircraftRole
Indicates that an aircraft is assigned or evaluated for a specific operational role or function.
-
C.
aircraftRoleSupported
Indicates that a given role or function is supported or enabled for a particular aircraft.
-
D.
aircraftRoleOfDesignatedAircraft
chosen
Indicates that an aircraft has the specified operational role or function as a designated aircraft within a particular context or mission.
-
E.
basedAircraftRole
Indicates that an aircraft is regularly stationed at a particular location in a specified operational role or function.
- 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_69f76e087bdc8190a4794bf9c0bd7634 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f49728c81908e49a5c13c31cb44 |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.