Triple
T35543278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese Checkers |
E1027121
|
entity |
| Predicate | teamPlay |
P99554
|
FINISHED |
| Object | allowed |
—
|
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: allowed | Statement: [Chinese Checkers, teamPlay, allowed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamPlay Context triple: [Chinese Checkers, teamPlay, allowed]
-
A.
teamAction
Indicates an action that is performed collectively by a group functioning as a team.
-
B.
team
Indicates that multiple entities are grouped together as a collaborative unit working toward shared goals or tasks.
-
C.
teamUpWith
Indicates forming a cooperative partnership or alliance with another entity to work together toward a shared goal.
-
D.
teamBased
Indicates that an activity, process, or structure is organized around collaboration within a group or team rather than by individuals working independently.
-
E.
cooperativePlay
chosen
Indicates that two or more entities are engaging in a shared, mutually coordinated activity or game toward a common goal.
- 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.