Triple
T26528615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosaura |
E670757
|
entity |
| Predicate | resolvesConflictWith |
P44088
|
FINISHED |
| Object | Astolfo |
—
|
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: Astolfo | Statement: [Rosaura, resolvesConflictWith, Astolfo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resolvesConflictWith Context triple: [Rosaura, resolvesConflictWith, Astolfo]
-
A.
conflictResolvedBy
Indicates that a conflict or dispute is settled or addressed through the actions, decisions, or intervention of a specified entity or process.
-
B.
conflictWith
Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
-
C.
addressedConflictWith
chosen
Indicates that one entity has taken action to confront, manage, or resolve a conflict involving another entity.
-
D.
appliesToConflictWith
Indicates that one element’s scope, rules, or effects are relevant to a conflict involving another element, defining how that element is implicated in or governed by the conflict.
-
E.
basedOnConflict
Indicates that one entity is derived from, influenced by, or structured around a particular conflict involving 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613f4ecb48190a463bde18f550279 |
completed | May 2, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:34 a.m.