Triple
T28991365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uralkali |
E736032
|
entity |
| Predicate | formerIndexMember |
P1168
|
FINISHED |
| Object | RTS Index |
—
|
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: RTS Index | Statement: [Uralkali, formerIndexMember, RTS Index]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerIndexMember Context triple: [Uralkali, formerIndexMember, RTS Index]
-
A.
formerMemberName
Indicates that the referenced name belongs to an entity that was previously a member of a particular group, organization, or body but is no longer one.
-
B.
formationMember
Indicates that an entity is a constituent part or member of a particular formation or organized group.
-
C.
formerMemberOf
chosen
Indicates that an entity once belonged to or was affiliated with a group, organization, or body, but is no longer a member.
-
D.
namedMember
Indicates that an entity is a member of a group, organization, or collection and is identified by a specific name within that membership context.
-
E.
firstMember
Indicates that one entity is the first member or element in an ordered collection or group relative to the others.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: April 28, 2026, 9:26 a.m.