Triple
T11589074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S&P BSE 500 |
E274830
|
entity |
| Predicate | hasSectorDiversification |
P14738
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [S&P BSE 500, hasSectorDiversification, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSectorDiversification Context triple: [S&P BSE 500, hasSectorDiversification, high]
-
A.
diversifiedIn
chosen
Indicates that an entity has expanded its involvement, investments, or activities across multiple different areas, sectors, or asset types.
-
B.
isNonDiversified
Indicates that an entity’s resources, investments, or activities are concentrated in a limited set of areas rather than being spread across a diverse range.
-
C.
sawDiversificationOf
Indicates that the subject experienced or witnessed a process in which something became more varied, diverse, or differentiated over time.
-
D.
hasBusinessDivision
Indicates that an organization includes or is composed of a specific business division as a subordinate unit.
-
E.
sectoralCoverage
Indicates the specific sectors, industries, or domains to which something (such as a policy, agreement, or dataset) applies or extends.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d89463360c8190b91228c46bfe2e5f |
completed | April 10, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.