Triple
T17768510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rome–Arno Campaign |
E443571
|
entity |
| Predicate | dateWithin |
P78870
|
FINISHED |
| Object | 1944 |
—
|
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: 1944 | Statement: [Rome–Arno Campaign, dateWithin, 1944]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateWithin Context triple: [Rome–Arno Campaign, dateWithin, 1944]
-
A.
occurredBetween
chosen
Indicates that an event or action took place within the time interval defined by two temporal boundaries.
-
B.
createdBetween
Indicates that something was created within a specified start and end time or date range.
-
C.
chronologicallyBetween
Indicates that one event or time point occurs after a first reference point and before a second reference point in temporal order.
-
D.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
-
E.
concludedBetween
Indicates that an agreement, arrangement, or formal relationship has been finalized between two or more parties.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e485fd8aa081909c8ee9264af15c69 |
completed | April 19, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:11 a.m.