Triple
T29759726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The North Pole (book) |
E753727
|
entity |
| Predicate | setsLocation |
P24794
|
FINISHED |
| Object | Greenland |
—
|
NE NERFINISHED |
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: Greenland | Statement: [The North Pole (book), setsLocation, Greenland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsLocation Context triple: [The North Pole (book), setsLocation, Greenland]
-
A.
setLocation
chosen
Indicates assigning or updating the place or position where an entity is located.
-
B.
definesLocation
Indicates that one entity specifies or establishes the spatial or geographic position of another entity.
-
C.
settingLocationType
Indicates the type or category of location in which an event, action, or situation takes place.
-
D.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
E.
subjectLocation
Indicates that one entity is located at, in, or near the place or position specified by another entity.
- 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f673cec6e88190842a2d724c9ee288 |
completed | May 2, 2026, 9:59 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 8:31 p.m.