Triple
T1082942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NDX |
E23986
|
entity |
| Predicate | sectorConcentration |
P71
|
FINISHED |
| Object | technology-heavy |
—
|
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: technology-heavy | Statement: [NDX, sectorConcentration, technology-heavy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectorConcentration Context triple: [NDX, sectorConcentration, technology-heavy]
-
A.
sectorInfluence
Indicates the degree to which one sector affects, shapes, or exerts control over another sector or over outcomes within that sector.
-
B.
sectorWeighting
Indicates the proportion or emphasis assigned to a particular sector within a broader portfolio, index, or classification.
-
C.
sector
chosen
Indicates that an entity operates in, belongs to, or is associated with a particular economic or industrial sector.
-
D.
sectorNeutral
Indicates that the relationship or action is independent of, or unaffected by, the specific sector or industry of the entities involved.
-
E.
industryConsortium
Indicates a collaborative association where multiple organizations formally join together within an industry to pursue shared goals, standards, or initiatives.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b95e56948190a1e92367ad7240b7 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73f4310819086281f8ec67d1a32 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.