Triple
T23067954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ocean at the edge of the world |
E575103
|
entity |
| Predicate | perceivedLocation |
P47308
|
FINISHED |
| Object | outer rim of the earth |
—
|
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: outer rim of the earth | Statement: [Ocean at the edge of the world, perceivedLocation, outer rim of the earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perceivedLocation Context triple: [Ocean at the edge of the world, perceivedLocation, outer rim of the earth]
-
A.
agingLocation
Indicates the place where an entity undergoes an aging process or is stored to age over time.
-
B.
possibleLocation
Indicates that an entity may be located at, or could plausibly occur in, a specified place or spatial context.
-
C.
subjectLocation
chosen
Indicates that one entity is located at, in, or near the place or position specified by another entity.
-
D.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
E.
plannedLocation
Indicates the intended or scheduled location where an entity is expected to be or an event is planned to occur.
- 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_69e245bd6e4c8190bb8942245b68cad5 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f189a5aa4081909b3f0dc92877323d |
completed | April 29, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:55 p.m.