Triple
T31012352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madrid–Barcelona high-speed line |
E790239
|
entity |
| Predicate | usedByServiceBrand |
P184611
|
FINISHED |
| Object | AVE |
—
|
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: AVE | Statement: [Madrid–Barcelona high-speed line, usedByServiceBrand, AVE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByServiceBrand Context triple: [Madrid–Barcelona high-speed line, usedByServiceBrand, AVE]
-
A.
usedBrand
Indicates that an entity has utilized, applied, or operated a particular brand in some context.
-
B.
usedBrandOf
Indicates that one entity made use of or operated an item, product, or service associated with a particular brand.
-
C.
usedOnBrand
Indicates that something (such as a product, material, or element) is applied to, associated with, or utilized in connection with a particular brand.
-
D.
usedByServiceTo
Indicates that something (such as a resource, component, or feature) is utilized or consumed by a particular service to perform its functions.
-
E.
usedInBrand
Indicates that something (such as a component, material, or element) is utilized as part of or within a particular brand.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7b365288c8190bcb11fcfba028737 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2f2b9ac8190aa05b8a1aa18ec2d |
completed | May 3, 2026, 8:41 p.m. |
Created at: April 29, 2026, 8:57 p.m.