Triple
T37277001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kabaty–Politechnika |
E924672
|
entity |
| Predicate | isSouthernSegmentOf |
P79806
|
FINISHED |
| Object | Warsaw Metro Line M1 |
—
|
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: Warsaw Metro Line M1 | Statement: [Kabaty–Politechnika, isSouthernSegmentOf, Warsaw Metro Line M1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSouthernSegmentOf Context triple: [Kabaty–Politechnika, isSouthernSegmentOf, Warsaw Metro Line M1]
-
A.
isSouthernBranchOf
Indicates that one entity functions as the southern subdivision or regional branch of another, larger organization or structure.
-
B.
isOnSouthernPartOf
chosen
Indicates that one entity is located on the southern part or southern region of another entity.
-
C.
hasSouthernTerminus
Indicates that one entity serves as the southern endpoint or terminus of another entity, such as a route, line, or path.
-
D.
isAlternateSegmentOf
Indicates that one segment serves as an alternative or substitute to another segment, typically in a sequence, structure, or path.
-
E.
isInSouthCentralPartOf
Indicates that one entity is located within the south-central region of another entity.
- 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_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.