Triple
T11045619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Zealand A netball team |
E261128
|
entity |
| Predicate | playerProfile |
P91407
|
FINISHED |
| Object | emerging elite players |
—
|
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: emerging elite players | Statement: [New Zealand A netball team, playerProfile, emerging elite players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerProfile Context triple: [New Zealand A netball team, playerProfile, emerging elite players]
-
A.
participantProfile
chosen
Indicates that an entity serves as the profile or descriptive record associated with a particular participant in an event, activity, or process.
-
B.
featuresPlayer
Indicates that something includes or prominently presents a particular player as part of its content or composition.
-
C.
publicProfile
Indicates that an entity’s profile or identifying information is visible and accessible to the general public.
-
D.
typicalPlayerProfile
Indicates the usual or characteristic attributes, behaviors, or demographics associated with a representative player in a given context.
-
E.
profileDirectory
Indicates the directory path where a user's or application's profile data is stored or managed.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7982f7e688190b3f0c249cd9b1a3e |
completed | April 9, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69d74407cb088190ba37c8da3d342b64 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.