Triple
T4468704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | July Crisis of 1914 |
E98440
|
entity |
| Predicate | occursInPeriod |
P56370
|
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: [July Crisis of 1914, occursInPeriod, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursInPeriod Context triple: [July Crisis of 1914, occursInPeriod, early 20th century]
-
A.
isSetInTimePeriod
chosen
Indicates that an event, story, or situation takes place within a specified time period.
-
B.
commonInPeriod
Indicates that something frequently occurs, appears, or is prevalent during a specified time period.
-
C.
refersToPeriod
Indicates that one entity designates, references, or is associated with a specific time period or interval.
-
D.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
-
E.
inForceInPeriod
Indicates that something (such as a rule, contract, or condition) is valid, applicable, or legally effective 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_69b3454b4ae481908967426dd37284d6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b356fb69a0819099f0005779f4fcac |
completed | March 13, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69b3563bf4f8819081726cde3a34460b |
completed | March 13, 2026, 12:11 a.m. |
Created at: March 12, 2026, 11:34 p.m.