Triple
T26955420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harriet Hayes |
E678888
|
entity |
| Predicate | networkCensorsConflict |
P162834
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Harriet Hayes, networkCensorsConflict, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkCensorsConflict Context triple: [Harriet Hayes, networkCensorsConflict, true]
-
A.
reportedConflict
Indicates that one party has formally reported the existence of a conflict involving another party or situation.
-
B.
numberOfConflicts
Indicates the count of distinct conflicts associated with or involving a given entity or situation.
-
C.
ledToConflict
Indicates that one event, action, or condition caused or significantly contributed to the emergence or escalation of a conflict between parties.
-
D.
internalConflict
Indicates a relationship where an entity experiences opposing desires, beliefs, or motives within itself, leading to psychological or emotional tension.
-
E.
subConflict
Indicates that one conflict is a component, phase, or subordinate part of a larger overarching conflict.
- F. None of above. chosen
Provenance (4 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_69eeeb4e75f08190b14fc91ca4a91488 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f62e4168a48190b45268f922780da6 |
completed | May 2, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62d5268ac8190835dc7119353b840 |
completed | May 2, 2026, 4:58 p.m. |
Created at: April 27, 2026, 6:27 a.m.