Triple
T13812621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pro D2 |
E331930
|
entity |
| Predicate | establishedAsSecondTier |
P18090
|
FINISHED |
| Object | 2000 |
—
|
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: 2000 | Statement: [Pro D2, establishedAsSecondTier, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsSecondTier Context triple: [Pro D2, establishedAsSecondTier, 2000]
-
A.
establishedAsTier
Indicates that one entity has been formally designated or set to operate at a particular tier or level within a defined hierarchy or system.
-
B.
demotedToSecondTierBy
Indicates that an entity’s status, rank, or priority has been reduced by another entity to a secondary or lower tier.
-
C.
secondTier
chosen
Indicates that something occupies a secondary or subordinate level of importance, quality, or rank relative to a primary or top tier.
-
D.
establishedAs
Indicates that one entity is formally created, designated, or recognized in a particular role, status, or identity as another entity.
-
E.
hasSecondDivision
Indicates that an entity possesses or is associated with a second-level division or subdivision within its structure or hierarchy.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de027198f8819095da3e714ac241f5 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc862e9608190bd8a3d883959b7e4 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:12 p.m.