Triple
T13115683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shoemaker Building |
E311086
|
entity |
| Predicate | coordinatePrecision |
P107884
|
FINISHED |
| Object | building level |
—
|
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: building level | Statement: [Shoemaker Building, coordinatePrecision, building level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinatePrecision Context triple: [Shoemaker Building, coordinatePrecision, building level]
-
A.
hasCoordinatePrecision
chosen
Indicates the degree of exactness or granularity with which an entity’s spatial coordinates are specified.
-
B.
coordinateFormat
Indicates the specific representation or notation used to express a set of coordinates.
-
C.
coordinatesMode
Indicates that one entity specifies or controls the coordinate system or reference frame used to interpret the spatial data of another entity.
-
D.
coordinateMeasured
Indicates that a specific coordinate value has been determined or recorded for an entity.
-
E.
coordinates
Indicates that one entity organizes, directs, or harmonizes the actions or efforts of another entity or group to achieve a unified outcome.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98180b6ac8190ae5a1f7c1480bd54 |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:06 p.m.