Triple
T17762014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Harald Coast |
E443399
|
entity |
| Predicate | locatedOnSideOfContinent |
P31095
|
FINISHED |
| Object | eastern side of Antarctica |
—
|
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: eastern side of Antarctica | Statement: [Prince Harald Coast, locatedOnSideOfContinent, eastern side of Antarctica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnSideOfContinent Context triple: [Prince Harald Coast, locatedOnSideOfContinent, eastern side of Antarctica]
-
A.
partlyLocatedOn
Indicates that one entity is situated such that only a portion of it lies on or within the spatial extent of another entity.
-
B.
situatedOnSideOf
chosen
Indicates that one entity is located along or beside the lateral part or edge of another entity.
-
C.
livedOnContinent
Indicates that an entity resided for a period of time on a specified continent.
-
D.
locatedOnTerritoryOf
Indicates that one entity is situated within or on the land area governed or owned by another entity.
-
E.
countryLocatedOn
Indicates that a country is geographically situated on or within the boundaries of a specified landmass, island, or continent.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e485f887ac81908c896a50175692b9 |
completed | April 19, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69e3cde9dc288190af0e2198487f2051 |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:11 a.m.