Triple
T22791009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ellsberg paradox |
E564108
|
entity |
| Predicate | canonicalSetup |
P149726
|
FINISHED |
| Object | two-urn problem |
—
|
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: two-urn problem | Statement: [Ellsberg paradox, canonicalSetup, two-urn problem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonicalSetup Context triple: [Ellsberg paradox, canonicalSetup, two-urn problem]
-
A.
typicalSetup
Indicates that an entity is arranged, configured, or organized in its standard or commonly used setup relative to another entity or context.
-
B.
frameworkEstablished
Indicates that a structured system of rules, guidelines, or components has been formally created and put in place to support or govern subsequent activities or relationships.
-
C.
canonicalPlacement
Indicates the standard or preferred position or arrangement of one entity relative to another within a defined structure or system.
-
D.
typicalInstallMethod
Indicates the usual or most common method by which something is installed or set up.
-
E.
controlledInstallation
Indicates that an entity has authoritative oversight or management responsibility over the setup, configuration, or deployment of another entity.
- 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_69e2455500788190b4b33030461f3bbd |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17c3545fc819084af67cc25e94839 |
completed | April 29, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:29 p.m.