Triple
T11962313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beasain |
E284697
|
entity |
| Predicate | hasRailwayCompanyOrigin |
P102515
|
FINISHED |
| Object | CAF founded in Beasain area |
—
|
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: CAF founded in Beasain area | Statement: [Beasain, hasRailwayCompanyOrigin, CAF founded in Beasain area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailwayCompanyOrigin Context triple: [Beasain, hasRailwayCompanyOrigin, CAF founded in Beasain area]
-
A.
hasRollingStockOrigin
Indicates that a piece of rolling stock originates from, or was initially based in, a particular location or source.
-
B.
railwayCompany
Indicates that one entity is a railway company that owns, operates, or manages railway services or infrastructure in relation to another entity.
-
C.
railwayCompanyOnRoute
Indicates that a particular railway company operates or provides service on a specified route.
-
D.
railwaySectorOrigin
Indicates the place or source from which a railway sector, line, or system originates or begins.
-
E.
railwayCompanyType
Indicates the specific category or classification of a railway company in terms of its role, ownership, or operational type.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9037848f481908276716675464464 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8dd0ba0f88190b7d5e358c27ca184 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 8, 2026, 9:45 p.m.