Triple
T10013793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Aircraft Corporation |
E199436
|
entity |
| Predicate | roleInConcorde |
P45538
|
FINISHED |
| Object | British partner |
—
|
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: British partner | Statement: [British Aircraft Corporation, roleInConcorde, British partner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInConcorde Context triple: [British Aircraft Corporation, roleInConcorde, British partner]
-
A.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
B.
roleInAirbus
Indicates that an entity holds or has held a specific role or position within Airbus.
-
C.
roleInEngine
Indicates the specific function or responsibility an entity has within an engine or engine-like system.
-
D.
collaboratorRole
chosen
Indicates the specific function, position, or capacity in which one collaborator participates in a shared activity or project with another.
-
E.
roleInNebula
Indicates that an entity holds a specific function, position, or involvement within a particular nebula.
- 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_69ca8315a1a08190ab310f25620f362b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd3e35508190920468be167cb708 |
completed | April 2, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69cd1da2cf9081908a6c0eb5247d0bc2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:52 p.m.