Triple
T37112661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ^BSESN |
E919031
|
entity |
| Predicate | hasBaseEntity |
P110019
|
FINISHED |
| Object | Bombay Stock Exchange Limited |
—
|
NE NERFINISHED |
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: Bombay Stock Exchange Limited | Statement: [^BSESN, hasBaseEntity, Bombay Stock Exchange Limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBaseEntity Context triple: [^BSESN, hasBaseEntity, Bombay Stock Exchange Limited]
-
A.
hasEntity
Indicates that one entity includes, contains, or is associated with another entity as part of its composition or context.
-
B.
hasBaseField
Indicates that one entity serves as the foundational or underlying field structure upon which another entity is defined or constructed.
-
C.
hasUnderlyingEntity
chosen
Indicates that one entity serves as the fundamental or base entity upon which another entity is conceptually or structurally built.
-
D.
hasSupportBaseIn
Indicates that one entity maintains an operational or organizational base of support located in another entity.
-
E.
hasBaseOn
Indicates that one entity is supported by, rests upon, or is structurally or conceptually founded on 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_69f76e9c57148190ba789dd059645bb9 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: May 3, 2026, 4:15 p.m.