Triple
T13615323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NAICS codes |
E325296
|
entity |
| Predicate | secondLevelName |
P110435
|
FINISHED |
| Object | subsector |
—
|
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: subsector | Statement: [NAICS codes, secondLevelName, subsector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondLevelName Context triple: [NAICS codes, secondLevelName, subsector]
-
A.
secondTier
Indicates that something occupies a secondary or subordinate level of importance, quality, or rank relative to a primary or top tier.
-
B.
secondLevelStructure
Indicates a relationship where one structure functions as a secondary or subordinate level within a larger, primary structure.
-
C.
secondLevelDomain
Indicates that one entity is the second-level domain associated with, or extracted from, another entity such as a full domain name or URL.
-
D.
secondGenerationName
Indicates that the object is the name given to the second generation derived from the subject.
-
E.
secondLevelRepresents
Indicates that one entity serves as a secondary or subordinate representation of another, typically refining or detailing the primary representation.
- 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_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. |
| PDg | Predicate description generation | batch_69dbbb8c77dc8190b7bd803b5e168d23 |
completed | April 12, 2026, 3:34 p.m. |
Created at: April 9, 2026, 9:50 p.m.