Triple
T18313674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jules Brunet |
E438695
|
entity |
| Predicate | timeInJapan |
P110760
|
FINISHED |
| Object | 1867-1869 |
—
|
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: 1867-1869 | Statement: [Jules Brunet, timeInJapan, 1867-1869]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInJapan Context triple: [Jules Brunet, timeInJapan, 1867-1869]
-
A.
modernDateInJapan
Indicates that a given date is interpreted or valid within the context of Japan’s modern calendar system (post–calendar reforms).
-
B.
travelTimeFromTokyoByShinkansen
Indicates the amount of time required to travel from Tokyo to another location using the Shinkansen (bullet train).
-
C.
timeInRegion
chosen
Indicates that a specified amount of time is spent, occurs, or is measured within a particular geographic or defined region.
-
D.
offsetFromJapanStandardTime
Indicates the time difference between a given time zone or time value and Japan Standard Time (JST), typically expressed as an offset in hours or minutes.
-
E.
timeZonePractice
Indicates that an entity conducts activities or operations according to a particular time zone or set of time zone rules.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5021b7e2c81908cd3b6684ab899f6 |
completed | April 19, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.