Triple
T12006524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phileas Fogg |
E285790
|
entity |
| Predicate | wagerGoal |
P102633
|
FINISHED |
| Object | to travel around the world in eighty days |
—
|
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: to travel around the world in eighty days | Statement: [Phileas Fogg, wagerGoal, to travel around the world in eighty days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wagerGoal Context triple: [Phileas Fogg, wagerGoal, to travel around the world in eighty days]
-
A.
goalIn
Indicates that one entity’s objective, aim, or intended outcome is located within, directed toward, or achieved inside another entity or context.
-
B.
laterGoal
Indicates that one goal occurs or is intended to be achieved after another goal in time.
-
C.
goalNumber
Indicates that an entity is associated with a specific target or objective quantified as a number.
-
D.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
-
E.
competitionGoal
Indicates that one entity’s objective or desired outcome is defined in the context of a competition involving 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903c5cfc08190821e4b2940c51416 |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902b245cc8190af96a9c2bd9c6250 |
completed | April 10, 2026, 2:01 p.m. |
| PDg | Predicate description generation | batch_69d9038e39f881908c58c19802ba2eb0 |
completed | April 10, 2026, 2:05 p.m. |
Created at: April 8, 2026, 9:46 p.m.