Triple
T27776963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kidz |
E699217
|
entity |
| Predicate | trackOnEdition |
P130083
|
FINISHED |
| Object | standard edition of Progress |
—
|
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: standard edition of Progress | Statement: [Kidz, trackOnEdition, standard edition of Progress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackOnEdition Context triple: [Kidz, trackOnEdition, standard edition of Progress]
-
A.
associatedWithEdition
Indicates a relationship where something is linked or connected to a specific edition of a work or resource.
-
B.
hasEditionIn
Indicates that one entity has a specific edition or version that exists or is available in another entity (such as a particular format, language, or location).
-
C.
hasOneTimeEdition
Indicates that an entity is associated with a single, non-recurring edition or version that occurs only once.
-
D.
isClosingTrackOnSomeEditions
chosen
Indicates that a track serves as the final (closing) track on certain editions or versions of a release, but not necessarily on all editions.
-
E.
notableEdition
Indicates that a particular edition or version of a work is especially significant or noteworthy in relation to that work.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 5:06 p.m.