Triple
T38164066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B3 São Paulo |
E953097
|
entity |
| Predicate | otherIndex |
P190172
|
FINISHED |
| Object | IBrX 50 |
—
|
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: IBrX 50 | Statement: [B3 São Paulo, otherIndex, IBrX 50]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: otherIndex Context triple: [B3 São Paulo, otherIndex, IBrX 50]
-
A.
associatedIndex
Indicates that one entity is linked to another through a corresponding index or positional reference.
-
B.
coreIndex
Indicates the position or identifier of an entity within a central or primary ordered structure (its core sequence or index).
-
C.
indexed
Indicates that one entity is organized, recorded, or referenced within a systematic index or catalog relative to another entity.
-
D.
indexer
Indicates a relationship where one entity organizes, catalogs, or creates an index for another entity’s contents or elements.
-
E.
mainIndex
Indicates that one entity serves as the primary or central index or reference point for another entity within a structured system.
- 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_69f76f0b93c48190a117319ab3a9f282 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcb089a8f881909aa9e722babd43f7 |
completed | May 7, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69fc45666c5c8190913bd632ac0e5b84 |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fcb088aac481909db90804faff315f |
completed | May 7, 2026, 3:32 p.m. |
Created at: May 3, 2026, 4:21 p.m.