Triple
T6604827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line 6 (Madrid Metro) |
E149086
|
entity |
| Predicate | isLoopLineAround |
P26846
|
FINISHED |
| Object | central Madrid |
—
|
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: central Madrid | Statement: [Line 6 (Madrid Metro), isLoopLineAround, central Madrid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLoopLineAround Context triple: [Line 6 (Madrid Metro), isLoopLineAround, central Madrid]
-
A.
isLoop
Indicates that something forms or behaves as a closed, repeating cycle or path that returns to its starting point.
-
B.
isOnLoopLine
Indicates that one entity (typically a route, track, or segment) lies on or belongs to a loop-shaped line or circuit within a network.
-
C.
formsLoopAround
chosen
Indicates that one entity extends or curves so as to create a closed loop encircling or surrounding another entity or region.
-
D.
isOnLoopSide
Indicates that one entity is located on the side or segment of a loop structure relative to another reference point or element.
-
E.
loopType
Indicates the specific kind or category of loop structure or iteration pattern used in a process or control flow.
- 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_69c687eaa7508190bb58ce2aa02039b3 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acfd17388190bd0bb8b2371e7df1 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:56 p.m.