Triple
T2156139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United First |
E47890
|
entity |
| Predicate | classAbove |
P4476
|
FINISHED |
| Object | United 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: United Economy | Statement: [United First, classAbove, United Economy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classAbove Context triple: [United First, classAbove, United Economy]
-
A.
above
Indicates that one entity is positioned higher than another along a vertical axis, without implying direct contact.
-
B.
classAfter
Indicates that one class or course occurs later in time or sequence than another class or course.
-
C.
hasHigherClass
chosen
Indicates that one entity belongs to a higher rank, level, or category in a hierarchy than another entity.
-
D.
hasStructureAbove
Indicates that one entity has another entity positioned vertically higher or located on top of it within a structural or spatial arrangement.
-
E.
inheritedFrom
Indicates that one entity has received or derived something (such as traits, rights, or property) from another entity, typically a predecessor or ancestor.
- 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_69a88a1d1fd8819088b34990d69a712f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe669c188190bb4c1c391ca848b0 |
completed | March 7, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69abbd9a60648190b20b116be5c7ad98 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.