Triple
T8632683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AGA |
E204439
|
entity |
| Predicate | supportsDualPlayfield |
P84347
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [AGA, supportsDualPlayfield, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDualPlayfield Context triple: [AGA, supportsDualPlayfield, yes]
-
A.
hasMultiplayer
Indicates that an entity (such as a game or application) supports a mode where multiple users can participate or interact simultaneously.
-
B.
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.
-
C.
hasDoublesPartner
Indicates that one entity serves as the doubles partner of another in a paired or team-based activity or sport.
-
D.
dualPair
Indicates that two entities form a dual pair, standing in a mathematically defined dual relationship where each is the dual counterpart of the other.
-
E.
supportsCrossPlay
Indicates that one platform, system, or service allows users on different platforms to interact or play together across those platforms.
- 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_69ca834b903c8190add96cc651e1a477 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc47944d1c819081f448f14d04bf9d |
completed | March 31, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69cc455d6d448190a2da2a319ac78c37 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc479284a8819099b0b0d879af3372 |
completed | March 31, 2026, 10:15 p.m. |
Created at: March 30, 2026, 6:27 p.m.