Triple
T9421803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roald Amundsen’s South Pole expedition 1910–1912 |
E227169
|
entity |
| Predicate | flagPlantedAtPole |
P88778
|
FINISHED |
| Object | Norwegian flag |
—
|
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: Norwegian flag | Statement: [Roald Amundsen’s South Pole expedition 1910–1912, flagPlantedAtPole, Norwegian flag]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flagPlantedAtPole Context triple: [Roald Amundsen’s South Pole expedition 1910–1912, flagPlantedAtPole, Norwegian flag]
-
A.
flagFlown
Indicates that a particular flag is being displayed or flown at a specific location or by a specific entity.
-
B.
flagpoleHeight
Indicates the height measurement of a flagpole relative to a specified reference (such as ground level).
-
C.
flagBearer
Indicates that one entity serves as the carrier or holder of a flag on behalf of another entity, group, or cause.
-
D.
flag
Indicates that one entity marks, signals, or draws attention to another entity, often to denote status, importance, or the need for review or action.
-
E.
flagOrInsignia
Indicates that one entity serves as a flag, emblem, or insignia representing another entity.
- F. None of above. chosen
Provenance (4 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_69ca84359e7c819091148ba4b670e436 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd6c2651c48190808281779fab49df |
completed | April 1, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69cca550777c819094e1851a6127cbbc |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:48 p.m.