Triple
T33851423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Outward Bound |
E867632
|
entity |
| Predicate | periodOfOriginalSetting |
P128598
|
FINISHED |
| Object | contemporary to early 1920s |
—
|
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: contemporary to early 1920s | Statement: [Outward Bound, periodOfOriginalSetting, contemporary to early 1920s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodOfOriginalSetting Context triple: [Outward Bound, periodOfOriginalSetting, contemporary to early 1920s]
-
A.
originalIntendedSetting
Indicates the context, environment, or circumstances for which something was initially designed or meant to be used.
-
B.
mainSettingPeriod
Indicates the historical or temporal period in which the primary setting of a work or event takes place.
-
C.
timePeriodOrigin
Indicates that one entity is the time period in which the other entity originated or first came into existence.
-
D.
eraOfSetting
chosen
Indicates the historical or temporal period in which the setting of something (such as a story, event, or work) takes place.
-
E.
settingPeriodDuration
Indicates the length of time for which a particular setting or configuration remains in effect.
- 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_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: May 1, 2026, 1:47 a.m.