Triple
T2847692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian School of economics |
E63019
|
entity |
| Predicate | viewOnValue |
P43388
|
FINISHED |
| Object | value is subjective |
—
|
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: value is subjective | Statement: [Austrian School of economics, viewOnValue, value is subjective]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOnValue Context triple: [Austrian School of economics, viewOnValue, value is subjective]
-
A.
viewOnState
Indicates that one entity holds or expresses a particular opinion, stance, or perspective regarding a specific state or condition.
-
B.
viewOnObject
Indicates that one entity directs its visual attention toward or observes another entity as an object of viewing.
-
C.
viewOnCustom
Indicates that one entity is being viewed, accessed, or displayed through a customized or user-defined view associated with another entity.
-
D.
viewOnFuture
Indicates a subject’s attitude, expectation, or perspective regarding future events or outcomes.
-
E.
viewOnSelf
Indicates a perspective where an entity directs its view, evaluation, or consideration toward itself.
- 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.