Triple
T746104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Peter’s Square tram stop |
E15343
|
entity |
| Predicate | hasIslandPlatforms |
P18595
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [St Peter’s Square tram stop, hasIslandPlatforms, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIslandPlatforms Context triple: [St Peter’s Square tram stop, hasIslandPlatforms, yes]
-
A.
hasNumberOfPlatforms
Indicates the relationship that specifies how many platforms are associated with a given entity.
-
B.
hasIsland
Indicates that one entity possesses, contains, or includes an island as part of its domain, territory, or structure.
-
C.
hasIslandArc
Indicates that one geographic or geological entity possesses or is associated with an island arc feature.
-
D.
hasTerminatingPlatforms
Indicates that the subject location or facility includes platforms where rail or transit services begin or end their routes, rather than passing through.
-
E.
hasViewingPlatform
Indicates that an entity includes or is equipped with a designated platform or area intended for viewing or observing something.
- 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a62ca1d081908e3191411f86498d |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a4ff10608190bfd60b4a1cb38f7d |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a57267c481909790a1fda3fced08 |
completed | March 1, 2026, 8:45 p.m. |
Created at: March 1, 2026, 7:37 p.m.