Triple
T34270898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kléber |
E879310
|
entity |
| Predicate | isOnLoopSectionOf |
P70109
|
FINISHED |
| Object | Line 6 |
—
|
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: Line 6 | Statement: [Kléber, isOnLoopSectionOf, Line 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnLoopSectionOf Context triple: [Kléber, isOnLoopSectionOf, Line 6]
-
A.
isOnSectionOf
chosen
Indicates that one entity is located on, or positioned along, a specific segment or subsection of another entity.
-
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.
isOnLoopSide
Indicates that one entity is located on the side or segment of a loop structure relative to another reference point or element.
-
D.
isLoopOf
Indicates that one entity represents a loop or cyclic structure corresponding to, derived from, or associated with another entity.
-
E.
isLoop
Indicates that something forms or behaves as a closed, repeating cycle or path that returns to its starting point.
- 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_69f349b4f5fc819094b441d18e95e5f1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:56 a.m.