Triple
T379651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curly McLain |
E8649
|
entity |
| Predicate | timePeriodOfFictionalSetting |
P302
|
FINISHED |
| Object | early 20th 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 20th century | Statement: [Curly McLain, timePeriodOfFictionalSetting, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfFictionalSetting Context triple: [Curly McLain, timePeriodOfFictionalSetting, early 20th century]
-
A.
fictionalUniverse
Indicates that two entities exist within, or are associated with, the same fictional universe or narrative setting.
-
B.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
C.
timeDescribedAs
Indicates that a specific time or temporal interval is characterized, labeled, or expressed using a particular description or representation.
-
D.
fictionalUniverseCreated
Indicates that one entity is the creator or originator of a particular fictional universe or setting in which stories or works take place.
-
E.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified time period.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec2b07248190979229bad3a741c9 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e964d4b481909290e474b0341e3c |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.