Triple
T33867184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Un Capitano Moro |
E868089
|
entity |
| Predicate | influenceOnOthello |
P157823
|
FINISHED |
| Object | basic plot structure |
—
|
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: basic plot structure | Statement: [Un Capitano Moro, influenceOnOthello, basic plot structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influenceOnOthello Context triple: [Un Capitano Moro, influenceOnOthello, basic plot structure]
-
A.
influenceOf
Indicates that one entity affects, shapes, or alters the state, behavior, or properties of another entity.
-
B.
wereInfluencedBy
Indicates that one entity’s ideas, actions, or characteristics were shaped or affected by another entity.
-
C.
influencedIn
Indicates that one entity had an effect on or shaped another entity within a specific context, domain, or setting.
-
D.
influencedAspectOf
chosen
Indicates that one entity has affected, shaped, or altered a particular aspect or component of another entity.
-
E.
incorporatesInfluence
Indicates that one entity integrates or absorbs the influence, ideas, or characteristics of another into itself.
- 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_69f34995029081909ede0f7df73d1a5e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 1, 2026, 1:47 a.m.