Triple
T35019811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing 737-600 |
E1010161
|
entity |
| Predicate | successorInMarketRole |
P22370
|
FINISHED |
| Object | Boeing 737-700 |
—
|
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: Boeing 737-700 | Statement: [Boeing 737-600, successorInMarketRole, Boeing 737-700]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorInMarketRole Context triple: [Boeing 737-600, successorInMarketRole, Boeing 737-700]
-
A.
successorInMarket
chosen
Indicates that one entity has taken over or followed another in serving the same market or customer base.
-
B.
successorRole
Indicates that one role or position directly follows and replaces another in a sequence or organizational structure.
-
C.
successorInSomeRoles
Indicates that one entity has taken over or followed another entity in certain specified roles or positions.
-
D.
successionRole
Indicates a role or position that one entity assumes as the successor to another in a sequence of holders or office-bearers.
-
E.
successorRoleInfluence
Indicates that one role affects, shapes, or determines the characteristics, responsibilities, or authority of the role that succeeds it.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00053d8004819097ad9cf6431a20a3 |
completed | May 10, 2026, 4:10 a.m. |
| PD | Predicate disambiguation | batch_6a0004b3a82c81908e2bf9a533a93eb6 |
completed | May 10, 2026, 4:08 a.m. |
Created at: May 3, 2026, 4:01 p.m.