Triple
T33228253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embraer ERJ 140 |
E850616
|
entity |
| Predicate | aircraftTypeDesignatorFamily |
P83140
|
FINISHED |
| Object | ERJ |
—
|
NE NERFINISHED |
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: ERJ | Statement: [Embraer ERJ 140, aircraftTypeDesignatorFamily, ERJ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftTypeDesignatorFamily Context triple: [Embraer ERJ 140, aircraftTypeDesignatorFamily, ERJ]
-
A.
aircraftFamilyIncludes
chosen
Indicates that a particular aircraft family encompasses or contains a given aircraft model or variant as a member of that family.
-
B.
commonAircraftFamily
Indicates that two aircraft belong to the same aircraft family or series, sharing a common design lineage.
-
C.
currentAircraftFamily
Indicates the specific family or series of aircraft that an entity is currently associated with or operating.
-
D.
aircraftType
Indicates the specific model or category of aircraft associated with an entity or event.
-
E.
notableAircraftFamily
Indicates that one entity is a well-known or historically significant family or series of aircraft associated with the other 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:30 a.m.