Triple
T760918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toulouse |
E16066
|
entity |
| Predicate | hostsCompanyFacilities |
P9342
|
FINISHED |
| Object | Airbus final assembly lines |
—
|
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: Airbus final assembly lines | Statement: [Toulouse, hostsCompanyFacilities, Airbus final assembly lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostsCompanyFacilities Context triple: [Toulouse, hostsCompanyFacilities, Airbus final assembly lines]
-
A.
hostsCompany
chosen
Indicates that one entity provides space, infrastructure, or support for a company to operate, be located, or hold activities.
-
B.
hasFacilities
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
-
C.
ownsFacilityOn
Indicates that one entity possesses ownership or control over a facility located on or associated with another entity (such as a site, property, or area).
-
D.
hostsTelescope
Indicates that one entity provides a location or facility where a telescope is installed, maintained, or operated.
-
E.
hasBackstageFacilities
Indicates that a venue or location provides backstage areas and related facilities for performers or staff.
- 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_69a493684ee48190bd43b7c78da4aec8 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a682e7d081909c9cd7839a49fb0b |
completed | March 1, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69a4a5048a8081908d0542214142664a |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.