Triple
T5261481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BA:US |
E118833
|
entity |
| Predicate | hasSectorClassification |
P24573
|
FINISHED |
| Object | Industrials |
—
|
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: Industrials | Statement: [BA:US, hasSectorClassification, Industrials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSectorClassification Context triple: [BA:US, hasSectorClassification, Industrials]
-
A.
isSectorSpecific
Indicates that something is tailored or restricted to a particular industry or sector rather than being generally applicable.
-
B.
sectorCode
Indicates the classification code that identifies the economic or organizational sector associated with an entity or activity.
-
C.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
D.
hasGICSSubIndustry
Indicates that an entity is classified within a specific GICS (Global Industry Classification Standard) sub-industry category.
-
E.
isClassifiedUnder
chosen
Indicates that one entity is categorized or grouped within a broader class, type, or category represented by 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bd0c5f48190a1be89314c59f96b |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.