Triple
T2541470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NLJ 500 |
E57792
|
entity |
| Predicate | hasRankingOrder |
P17947
|
FINISHED |
| Object | descending by headcount |
—
|
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: descending by headcount | Statement: [NLJ 500, hasRankingOrder, descending by headcount]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRankingOrder Context triple: [NLJ 500, hasRankingOrder, descending by headcount]
-
A.
hasRankOrder
chosen
Indicates that one entity is ordered or positioned relative to others according to a specific ranking or sequence.
-
B.
hasRankingCategory
Indicates that an entity is associated with a particular ranking category or tier within an ordered classification system.
-
C.
hasRankingUnit
Indicates that one entity is associated with a specific unit or scale used to express its ranking or ordered position.
-
D.
hasRankCategory
Indicates that an entity is assigned to a particular rank-based classification or level within an ordered hierarchy.
-
E.
hasRankLevels
Indicates that an entity is associated with one or more hierarchical rank levels within a ranking or grading system.
- 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2bc7b5481908b3664495e99f1a4 |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0c63964819092d5f578195ae8dd |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:47 p.m.