Triple
T3943326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucani |
E92085
|
entity |
| Predicate | eventuallyBecame |
P6579
|
FINISHED |
| Object | Roman allies |
—
|
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: Roman allies | Statement: [Lucani, eventuallyBecame, Roman allies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventuallyBecame Context triple: [Lucani, eventuallyBecame, Roman allies]
-
A.
became
chosen
Indicates a change of state or status in which one entity transitions into or assumes the role, condition, or identity of another.
-
B.
eventuallyBefriends
Indicates that one entity, after some passage of time or intervening events, comes to form a friendly or amicable relationship with another entity.
-
C.
didNotBecome
Indicates that an expected or potential change of state, role, or condition between entities did not occur.
-
D.
emergedWith
Indicates that one entity came forth, appeared, or became visible at the same time and in association with another entity.
-
E.
transitionedInto
Indicates that one entity changed state, form, role, or condition to become another specified state or entity.
- 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_69aed965502c8190904ebad1203a4ae8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee764235081909309b3c982f322a9 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:24 p.m.