Triple
T25210695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arco della Pace |
E631675
|
entity |
| Predicate | laterCompletedUnder |
P167252
|
FINISHED |
| Object | Austrian Empire |
—
|
NE NERFINISHED |
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: Austrian Empire | Statement: [Arco della Pace, laterCompletedUnder, Austrian Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterCompletedUnder Context triple: [Arco della Pace, laterCompletedUnder, Austrian Empire]
-
A.
completedAfter
Indicates that one event or task was finished at a later time than another specified event or task.
-
B.
alsoCompletedBy
Indicates that the same task, activity, or item has been completed by an additional agent or entity besides the one already referenced.
-
C.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
D.
workCompletedAfter
Indicates that one entity’s work or task was finished at a later time than another specified work or task.
-
E.
completionOf
Indicates that one entity represents the finished state, fulfillment, or successful conclusion of another entity, process, or requirement.
- F. None of above. chosen
Provenance (4 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_69e75a8d1aa48190a4320acd3654762c |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 21, 2026, 12:58 p.m.