Triple
T13615322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NAICS codes |
E325296
|
entity |
| Predicate | topLevelName |
P80513
|
FINISHED |
| Object | sector |
—
|
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: sector | Statement: [NAICS codes, topLevelName, sector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topLevelName Context triple: [NAICS codes, topLevelName, sector]
-
A.
topLevelOf
Indicates that one entity is the highest or most overarching level within the structure or hierarchy of another entity.
-
B.
topLevel
chosen
Indicates that an entity occupies the highest or outermost level in a hierarchy, structure, or organizational arrangement, with no parent above it.
-
C.
topLevelHierarchy
Indicates that an entity occupies the highest position or root level within a hierarchical structure, with no parent above it.
-
D.
topLevelRepresents
Indicates that one entity serves as the primary or overarching representation of another entity or concept at the highest level of abstraction or organization.
-
E.
hasTopLevel
Indicates that one entity is the highest or primary element within a hierarchy or structure relative to another entity.
- 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_69d8076aae28819092cf636190ee5529 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae1b3ee481909bd43ded6227a3e5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:50 p.m.