Triple
T14385694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In Contradiction |
E356716
|
entity |
| Predicate | defendsPosition |
P114035
|
FINISHED |
| Object | some contradictions are 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: some contradictions are true | Statement: [In Contradiction, defendsPosition, some contradictions are true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defendsPosition Context triple: [In Contradiction, defendsPosition, some contradictions are true]
-
A.
defends
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
B.
defendedAs
Indicates that one entity is presented, argued, or justified as being equivalent to or serving the role of another entity in a defensive or protective context.
-
C.
defendantPosition
Indicates the role, stance, or location that a defendant holds within a legal case or proceeding.
-
D.
defendedOn
Indicates that one entity protected, supported, or argued in favor of another entity during a specific time or event.
-
E.
defenseArgument
Indicates that an entity presents or supports a line of reasoning intended to defend or justify another entity, often in a legal or argumentative context.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9025cff881908c08224d90d9f750 |
completed | April 14, 2026, 7:06 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
| PDg | Predicate description generation | batch_69de2e08b6c08190bb4c929deab236a6 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:16 a.m.