Triple
T28411141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italic Confederation |
E719663
|
entity |
| Predicate | demandDirectedAt |
P40218
|
FINISHED |
| Object | Roman Senate |
—
|
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: Roman Senate | Statement: [Italic Confederation, demandDirectedAt, Roman Senate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demandDirectedAt Context triple: [Italic Confederation, demandDirectedAt, Roman Senate]
-
A.
directedTo
chosen
Indicates that something is sent, aimed, or addressed toward a particular target or recipient.
-
B.
demand
Indicates that one entity requests or insists that another entity provide something or perform an action, often with an expectation of compliance.
-
C.
demandSide
Indicates a relationship where an entity represents or pertains to the consumer or buyer side of a market, focusing on demand rather than supply.
-
D.
promptedDemandFor
Indicates that one entity’s action or occurrence caused an increase in demand for another entity.
-
E.
demanded
Indicates that one entity forcefully or insistently requested something from another 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64dbc9be4819082633afaeb8136dc |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 1:27 a.m.