Triple
T32405753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Line A branch |
E828072
|
entity |
| Predicate | wasSurfaceLine |
P174042
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Green Line A branch, wasSurfaceLine, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasSurfaceLine Context triple: [Green Line A branch, wasSurfaceLine, true]
-
A.
isLinedWith
Indicates that one object or surface is covered, edged, or internally coated along its length or area with another material or layer.
-
B.
hasSurfaceLevel
Indicates that one entity possesses or is characterized by a particular degree or measure of surface level (e.g., depth, detail, or superficiality).
-
C.
definedLine
Indicates that a specific line (such as a boundary, path, or reference line) has been formally established or specified within a given context.
-
D.
usesSurface
Indicates that one entity employs or interacts with another entity as a surface or platform for its action or function.
-
E.
линия
Indicates a relationship where something is a line or forms a linear connection or boundary between points or areas.
- 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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c247928481908f5aa369adfd2906 |
completed | May 3, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bb344bb48190a8089f29c0063ded |
completed | May 3, 2026, 3:04 a.m. |
Created at: May 1, 2026, 12:53 a.m.