Triple
T34224954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mansion House, Dublin |
E878018
|
entity |
| Predicate | hasCoordinatesSystem |
P22467
|
FINISHED |
| Object | WGS84 |
—
|
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: WGS84 | Statement: [Mansion House, Dublin, hasCoordinatesSystem, WGS84]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoordinatesSystem Context triple: [Mansion House, Dublin, hasCoordinatesSystem, WGS84]
-
A.
hasCoordinates
Indicates that an entity is associated with specific spatial coordinates that define its position in a given reference system.
-
B.
hasCoordinatesType
chosen
Indicates that an entity is associated with a specific type or system of coordinates used to define its position.
-
C.
coordinateSystem
Indicates that one entity defines or uses a particular spatial or reference coordinate system in relation to another entity.
-
D.
coordinateSystemFor
Indicates that one entity serves as the coordinate system or reference frame used to define the position, orientation, or measurement of another entity.
-
E.
hasGeographicalCoordinateSystem
Indicates that something uses or is defined within a specific geographical coordinate system for locating positions on the Earth’s surface.
- 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_69f349b16d0481908754e3069f05e0c1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:55 a.m.