Triple
T17229626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | socialist calculation debate |
E418206
|
entity |
| Predicate | hasImportantConcept |
P531
|
FINISHED |
| Object | economic calculation 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: economic calculation problem | Statement: [socialist calculation debate, hasImportantConcept, economic calculation problem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImportantConcept Context triple: [socialist calculation debate, hasImportantConcept, economic calculation problem]
-
A.
hasCriticalConcept
Indicates that one entity includes, depends on, or is defined by a key concept that is essential to understanding or functioning of another entity.
-
B.
hasConcept
chosen
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
C.
introducedConcept
Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity or context.
-
D.
hasTwoKeyConcepts
Indicates that a subject is associated with exactly two distinct key concepts.
-
E.
isImportantFor
Indicates that something holds significant value, relevance, or necessity in relation to something else.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42df62ec48190b2ed633a5bcc0255 |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.