Triple
T31471598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saved |
E802872
|
entity |
| Predicate | isControversial |
P115124
|
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: [Saved, isControversial, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isControversial Context triple: [Saved, isControversial, true]
-
A.
controversialBecause
Indicates that one entity is considered controversial specifically due to, or as a result of, its relationship with or association to another entity.
-
B.
controversialStatus
chosen
Indicates that the subject is associated with debate, dispute, or disagreement regarding its acceptance, validity, or appropriateness.
-
C.
hasControversialAspect
Indicates that something includes an element, feature, or aspect that is disputed, debated, or likely to cause disagreement or public criticism.
-
D.
controversy
Indicates a situation in which there is active disagreement, dispute, or public debate between parties over a particular issue, action, or claim.
-
E.
controversyType
Indicates the specific kind or category of controversy associated with an entity or situation.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 30, 2026, 9:26 p.m.