Triple
T6892070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basque pelota |
E159070
|
entity |
| Predicate | canBePlayedSingles |
P43217
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Basque pelota, canBePlayedSingles, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBePlayedSingles Context triple: [Basque pelota, canBePlayedSingles, true]
-
A.
canAlsoBePlayedIn
Indicates that something (such as a game, media, or activity) is additionally playable or usable in another context, format, or environment beyond its primary one.
-
B.
hasSinglePlayer
chosen
Indicates that something includes, supports, or is designed for a single-player mode or experience.
-
C.
mainSingles
Indicates that the subject is the primary or most prominent single(s) released from the associated work or artist.
-
D.
playableWith
Indicates that one entity can be used, engaged, or interacted with together alongside another entity, typically in a compatible or cooperative manner.
-
E.
hasDoublesPartner
Indicates that one entity serves as the doubles partner of another in a paired or team-based activity or sport.
- 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_69c6883568c8819081db6407e892cccc |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d92ecbdc8190992f9c7f4f33f4c4 |
completed | March 27, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b53e9881909ec298daa9f1913b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:24 p.m.