Triple
T2131185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RM |
E46541
|
entity |
| Predicate | usedInHistoricalEra |
P3656
|
FINISHED |
| Object | interwar period |
—
|
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: interwar period | Statement: [RM, usedInHistoricalEra, interwar period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInHistoricalEra Context triple: [RM, usedInHistoricalEra, interwar period]
-
A.
historicalPeriodOfUse
chosen
Indicates the time period during which something was in active use or commonly utilized.
-
B.
historicalEraUsheredIn
Indicates the historical era or period that was initiated or brought about as a result of a particular event, action, or entity.
-
C.
partOfEra
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
-
D.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
-
E.
historicallyIn
Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
- 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_69a88a1626548190ae59a5028c3baa8e |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbb79f21881909ad8d1a09c1f29fd |
completed | March 7, 2026, 5:45 a.m. |
| PD | Predicate disambiguation | batch_69abb7bf56e481909b0f497d238451cc |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.