Triple
T21537394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cadillac |
E531383
|
entity |
| Predicate | depthInSystemRanking |
P1536
|
FINISHED |
| Object | 47th deepest |
—
|
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: 47th deepest | Statement: [Cadillac, depthInSystemRanking, 47th deepest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depthInSystemRanking Context triple: [Cadillac, depthInSystemRanking, 47th deepest]
-
A.
depthRank
chosen
Indicates the relative ordering of entities based on how deep or distant they are along a specified depth dimension or hierarchy.
-
B.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
C.
rankedAs
Indicates that one entity is assigned a specific position or level in an ordered ranking relative to others.
-
D.
heightRankWithinStructure
Indicates the relative ordering of an entity’s height compared to other entities within the same structure.
-
E.
capacityRank
Indicates the relative ordering of entities based on how much capacity (e.g., volume, throughput, or capability) they possess compared to others.
- 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_69e0c45e5b8881908ac18fc2f493b114 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee9d0fdf448190b47ac7c28904f86b |
completed | April 26, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:27 p.m.