Triple
T13088125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warsaw Pact airlines |
E310389
|
entity |
| Predicate | typicalEconomicSystem |
P252
|
FINISHED |
| Object | planned economy |
—
|
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: planned economy | Statement: [Warsaw Pact airlines, typicalEconomicSystem, planned economy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEconomicSystem Context triple: [Warsaw Pact airlines, typicalEconomicSystem, planned economy]
-
A.
economicSystem
chosen
Indicates the type or structure of the economic organization or system under which an entity operates or to which it belongs.
-
B.
positionOnEconomicSystem
Indicates the stance or viewpoint an entity holds regarding a particular economic system or model.
-
C.
economicFramework
Indicates the overarching system of principles, rules, and structures that organize and govern economic activities and relationships.
-
D.
regionalEconomyType
Indicates the type or classification of an economy associated with a specific region.
-
E.
economicExtensionOf
Indicates that one entity’s economy is heavily dependent on, controlled by, or functions as an outgrowth of another entity’s economic system.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d981378dd08190b4f00e4e5df0e480 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:02 p.m.