Triple
T21294241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TIA-942 |
E524873
|
entity |
| Predicate | tierSystemRangesFrom |
P143617
|
FINISHED |
| Object | Tier 1 to Tier 4 |
—
|
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: Tier 1 to Tier 4 | Statement: [TIA-942, tierSystemRangesFrom, Tier 1 to Tier 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tierSystemRangesFrom Context triple: [TIA-942, tierSystemRangesFrom, Tier 1 to Tier 4]
-
A.
tier2Range
Indicates that the value or entity falls within the defined second-level (tier 2) range of a multi-tiered scale or classification.
-
B.
tier1Range
Indicates that something falls within the defined bounds or limits of the first (or primary) tier in a tiered range system.
-
C.
tier3Range
Indicates that one entity falls within the defined third-level (tier 3) range or interval relative to another entity or reference scale.
-
D.
rankRange
Indicates that an entity’s rank falls within a specified minimum and maximum range.
-
E.
tierConfiguration
Indicates how entities are organized or assigned into different levels or tiers according to a defined configuration or scheme.
- 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_69e0b517e6748190850d6f6ddf323d69 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73856ba988190a8359efecea362cc |
completed | April 21, 2026, 8:41 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 4:04 p.m.