Triple
T592470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexandria tram |
E17305
|
entity |
| Predicate | yellowNetworkArea |
P4903
|
FINISHED |
| Object | central Alexandria |
—
|
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 Alexandria | Statement: [Alexandria tram, yellowNetworkArea, central Alexandria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yellowNetworkArea Context triple: [Alexandria tram, yellowNetworkArea, central Alexandria]
-
A.
navigationArea
Indicates that a specified region or space is designated for movement, routing, or pathfinding within an environment.
-
B.
connectsArea
Indicates that one area serves as a link or passage between two other areas, enabling movement or interaction between them.
-
C.
hillColor
Indicates the color attribute associated with a hill.
-
D.
hasAreaCode
Indicates that a specified telephone area code is assigned to or associated with a particular geographic region, location, or phone service entity.
-
E.
networkCoverage
chosen
Indicates the extent to which a network’s signal or service is available across a given area or to specific entities.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bbcaf5c81908de4e27096d3da13 |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494cd7d3c8190af008acf34a2293b |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.