Triple
T28014994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ineos Grenadiers |
E707523
|
entity |
| Predicate | UCICode |
P163626
|
FINISHED |
| Object | IGD |
—
|
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: IGD | Statement: [Ineos Grenadiers, UCICode, IGD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UCICode Context triple: [Ineos Grenadiers, UCICode, IGD]
-
A.
MICCode
Indicates the industry classification relationship between an entity and its Market Identifier Code (MIC) used to categorize its market or sector.
-
B.
iauCode
Indicates the standardized code assigned by the International Astronomical Union (IAU) to uniquely identify an astronomical object or entity.
-
C.
UICCompanyCode
Indicates a relationship where a specific company is identified or classified by its unique UIC (Uniform Identification Code) company code.
-
D.
ICCCode
Indicates that an entity is associated with a specific International Criminal Court (ICC) code, identifying its classification or legal reference under ICC standards.
-
E.
UICClassification
Indicates the standardized classification or coding assigned to an entity according to the UIC (International Union of Railways) system.
- F. None of above. chosen
Provenance (4 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63c069ddc819089f07c71eaedeade |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 8:06 p.m.