Triple
T29538717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Harbour |
E749424
|
entity |
| Predicate | isLocatedOnPeninsula |
P10961
|
FINISHED |
| Object | Burin Peninsula |
—
|
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: Burin Peninsula | Statement: [Red Harbour, isLocatedOnPeninsula, Burin Peninsula]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedOnPeninsula Context triple: [Red Harbour, isLocatedOnPeninsula, Burin Peninsula]
-
A.
locatedOnPeninsula
chosen
Indicates that one entity is situated on or within the geographic area of a peninsula.
-
B.
isPartOfPeninsula
Indicates that one geographic entity is located within and forms a component of a larger peninsula.
-
C.
isPeninsula
Indicates that a landform is a peninsula, meaning it is surrounded by water on most sides but connected to a larger landmass.
-
D.
containsPeninsula
Indicates that one geographic region fully or partially includes a landform that is a peninsula within its boundaries.
-
E.
peninsulaBetween
Indicates that one landmass forms a peninsula situated between two other geographic entities, separating or partially separating them.
- 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_69f0bd47abb081909bd6e6a33d770fd8 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 28, 2026, 5 p.m.