Triple
T9421802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roald Amundsen’s South Pole expedition 1910–1912 |
E227169
|
entity |
| Predicate | beatRivalToPoleByDays |
P88777
|
FINISHED |
| Object | about 33 |
—
|
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: about 33 | Statement: [Roald Amundsen’s South Pole expedition 1910–1912, beatRivalToPoleByDays, about 33]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beatRivalToPoleByDays Context triple: [Roald Amundsen’s South Pole expedition 1910–1912, beatRivalToPoleByDays, about 33]
-
A.
rivalryPeriod
Indicates the time span during which two entities are engaged in an ongoing rivalry or competitive relationship.
-
B.
racesAgainst
Indicates that one entity competes in a race directly against another entity.
-
C.
peakDays
Indicates the days on which something reaches its highest or most intense level of activity, usage, or occurrence.
-
D.
peakDay
Indicates the specific day on which a quantity, activity, or effect reaches its maximum level within a given period.
-
E.
raceDayIncludes
Indicates that a particular race day schedule or event set contains or encompasses a specific race or racing-related activity.
- 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.