Triple
T34410081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S&P/NZX indices |
E883230
|
entity |
| Predicate | launchedInCollaborationWith |
P182873
|
FINISHED |
| Object | NZX 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: NZX Limited | Statement: [S&P/NZX indices, launchedInCollaborationWith, NZX Limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchedInCollaborationWith Context triple: [S&P/NZX indices, launchedInCollaborationWith, NZX Limited]
-
A.
establishedInCollaborationWith
Indicates that something was created, founded, or set up jointly through cooperative effort between two or more parties.
-
B.
organizedInCollaborationWith
Indicates that an event, project, or activity was organized jointly in cooperation with another party or parties.
-
C.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
D.
launchedWithSponsor
Indicates that an entity was initiated, released, or started in association with a sponsoring organization or individual.
-
E.
publishedInCollaborationWith
Indicates that an entity was published as a result of a joint effort or partnership with another entity.
- 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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f794f24e588190965e39b77534d53f |
completed | May 3, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f791cad5e08190a8a04ca283dbecaa |
completed | May 3, 2026, 6:19 p.m. |
Created at: May 1, 2026, 1:59 a.m.