Triple
T38108213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Franklin |
E951579
|
entity |
| Predicate | contemporaneousSetting |
P20834
|
FINISHED |
| Object | 14th-century England (fictionalized) |
—
|
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: 14th-century England (fictionalized) | Statement: [the Franklin, contemporaneousSetting, 14th-century England (fictionalized)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contemporaneousSetting Context triple: [the Franklin, contemporaneousSetting, 14th-century England (fictionalized)]
-
A.
contemporaryWith
Indicates that two entities existed, occurred, or were active during the same time period.
-
B.
contemporaryPresenceIn
Indicates that an entity exists or is present in a particular place, context, or timeframe at the same time as another specified reference point or entity.
-
C.
contemporary
Indicates that two entities exist, occur, or are active during the same time period or historical era.
-
D.
placeOfSetting
chosen
Indicates the location or environment where an event, scene, or situation takes place.
-
E.
contemporaryState
Indicates that two entities exist or occur during the same time period or historical era.
- 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_69f76f065ed08190bdfb1b6d817f5b39 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 3, 2026, 4:21 p.m.