Triple
T24956270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grindfather |
E624479
|
entity |
| Predicate | createdForContext |
P141130
|
FINISHED |
| Object | NBA competition |
—
|
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: NBA competition | Statement: [Grindfather, createdForContext, NBA competition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdForContext Context triple: [Grindfather, createdForContext, NBA competition]
-
A.
createdFor
Indicates that one entity was made, produced, or designed specifically to serve, benefit, or be used by another entity.
-
B.
creatorContext
chosen
Indicates the situational or environmental context in which a creator produced or is associated with a work or entity.
-
C.
creatorOfContext
Indicates that one entity is the originator or producer of the surrounding situation, environment, or framework in which another entity exists or operates.
-
D.
emergedInContext
Indicates that something came into existence, became apparent, or developed within a specific situation, environment, or set of circumstances.
-
E.
createdForAdaptation
Indicates that one entity was created specifically to serve as an adaptation of another entity, such as transforming the original into a new medium, format, or version.
- 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_69e2ff23a3a88190b1b9743fe5e15f94 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 5:57 a.m.