Triple
T26968038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Encuentro Social |
E679226
|
entity |
| Predicate | hasConservativePlatform |
P179528
|
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: [Encuentro Social, hasConservativePlatform, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConservativePlatform Context triple: [Encuentro Social, hasConservativePlatform, true]
-
A.
hasConservatism
Indicates that one entity possesses, exhibits, or is characterized by a tendency toward conservatism in behavior, beliefs, or practices.
-
B.
isConservative
chosen
Indicates that an entity holds or supports conservative views, values, or positions in a given context.
-
C.
hasConservativeFaction
Indicates that an entity includes or is associated with a subgroup characterized by conservative views or positions.
-
D.
isConservativeOver
Indicates that one entity preserves or does not increase a certain property, measure, or effect when applied over or in relation to another entity.
-
E.
identifiesAsConservativeLineageTo
Indicates that one entity regards another as belonging to, or continuing, a conservative ideological or traditional lineage.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fe991bca608190b524e419642f4243 |
completed | May 9, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69fe979fc1c4819091fc48d63ea12063 |
completed | May 9, 2026, 2:10 a.m. |
Created at: April 27, 2026, 6:37 a.m.