Triple
T31703265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act I (A Lie of the Mind) |
E809113
|
entity |
| Predicate | introducesConflictBetween |
P89395
|
FINISHED |
| Object | Jake and Beth |
—
|
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: Jake and Beth | Statement: [Act I (A Lie of the Mind), introducesConflictBetween, Jake and Beth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducesConflictBetween Context triple: [Act I (A Lie of the Mind), introducesConflictBetween, Jake and Beth]
-
A.
conflictWith
Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
-
B.
triggersConflict
Indicates that one entity initiates or causes a dispute, clash, or incompatibility to arise with another entity or within a system.
-
C.
conflictIntroduced
chosen
Indicates that a conflict has been newly created or brought into existence between the related entities.
-
D.
reportedConflict
Indicates that one party has formally reported the existence of a conflict involving another party or situation.
-
E.
mentionsConflict
Indicates that one entity refers to or discusses a dispute, disagreement, or 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: April 30, 2026, 11:12 p.m.