Triple
T1207682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Master and Commander: The Far Side of the World |
E25925
|
entity |
| Predicate | timeSetting |
P20835
|
FINISHED |
| Object | early 19th century |
—
|
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: early 19th century | Statement: [Master and Commander: The Far Side of the World, timeSetting, early 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSetting Context triple: [Master and Commander: The Far Side of the World, timeSetting, early 19th century]
-
A.
timeOfSetting
chosen
Indicates the specific time at which an event, object, or phenomenon is set, scheduled, or takes place.
-
B.
timeType
Indicates the specific temporal category or classification associated with a time-related entity or value (e.g., duration, point in time, interval, or recurrence type).
-
C.
timeSystem
Indicates a relationship where an entity uses, follows, or is defined within a particular system for measuring or organizing time.
-
D.
time
Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
-
E.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
- 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_69a4942b30f08190a91c60573e16b5ef |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bdc483b481908e5bfef5d2f4fc5a |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6078088190ba0221ae3368416c |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.