Triple
T1900388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caesar’s civil war |
E37676
|
entity |
| Predicate | hasSymbolicEvent |
P16925
|
FINISHED |
| Object | “alea iacta est” (the die is cast) at the Rubicon |
—
|
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: “alea iacta est” (the die is cast) at the Rubicon | Statement: [Caesar’s civil war, hasSymbolicEvent, “alea iacta est” (the die is cast) at the Rubicon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSymbolicEvent Context triple: [Caesar’s civil war, hasSymbolicEvent, “alea iacta est” (the die is cast) at the Rubicon]
-
A.
containsSymbolicAct
chosen
Indicates that one entity includes or incorporates a symbolic action or gesture associated with another entity.
-
B.
hasSymbolicValue
Indicates that something holds meaning, significance, or representational value beyond its literal or practical function.
-
C.
hasEventType
Indicates that an event is associated with, or classified under, a specific type or category of event.
-
D.
hasSubEvent
Indicates that an event is composed of, or includes as part of its structure, another event that occurs within it.
-
E.
hasEventSpace
Indicates that an entity provides or includes a designated space intended for hosting events.
- 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_69a8861be7148190a680937ec451a304 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb18c46c88190b10c05bf5c6a2d9c |
completed | March 7, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69abafe7e7e88190b58c0df59187c0c2 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.