Triple
T2847696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian School of economics |
E63019
|
entity |
| Predicate | viewOnCapital |
P43389
|
FINISHED |
| Object | capital is heterogeneous |
—
|
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: capital is heterogeneous | Statement: [Austrian School of economics, viewOnCapital, capital is heterogeneous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOnCapital Context triple: [Austrian School of economics, viewOnCapital, capital is heterogeneous]
-
A.
accessToCapital
Indicates that one entity provides or enables financial resources or funding for another entity to use.
-
B.
containsCapitalOf
Indicates that one location geographically includes the city that serves as the capital of another region or entity.
-
C.
capitalCityObservedIn
Indicates that a particular capital city was observed, recorded, or identified within a specified context, location, or time frame.
-
D.
containsCapitalCity
Indicates that a geographic or political region includes within its boundaries the capital city associated with it.
-
E.
hasScenicViewOf
Indicates that one entity offers a visually appealing or picturesque view 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_69ab4c407c408190857d25e027155ce9 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf403698819084fb4ace5839aa05 |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd0e86808190bcefffafbd3cd441 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde2cdcc48190827195d3ae70aa19 |
completed | March 7, 2026, 8:13 a.m. |
Created at: March 6, 2026, 10:02 p.m.