Triple
T14775385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alban–Roman conflict settlement |
E347245
|
entity |
| Predicate | outcomeForAlbaLonga |
P115743
|
FINISHED |
| Object | subordination to Rome |
—
|
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: subordination to Rome | Statement: [Alban–Roman conflict settlement, outcomeForAlbaLonga, subordination to Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeForAlbaLonga Context triple: [Alban–Roman conflict settlement, outcomeForAlbaLonga, subordination to Rome]
-
A.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
B.
outcomeForByzantines
Indicates the result or consequence experienced by the Byzantines in relation to a specific event, action, or situation.
-
C.
outcomeOfTrial
Indicates that a particular result or verdict is produced as the consequence of a specific trial or legal proceeding.
-
D.
outcomeInvolvement
Indicates that an entity is involved in producing, influencing, or being affected by a particular outcome or result.
-
E.
outcomeType
Indicates the specific category or nature of the result produced by an event, process, or action.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec815dd5081909e927911c06b2d66 |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:31 a.m.