Triple
T11547528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyrian |
E273808
|
entity |
| Predicate | playerJoinable |
P64765
|
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: [Kyrian, playerJoinable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerJoinable Context triple: [Kyrian, playerJoinable, true]
-
A.
canJoin
chosen
Indicates that one entity is permitted or able to become a member or participant in another entity or group.
-
B.
hasPlayer
Indicates that an entity (such as a team, game, or roster) includes or is associated with a specific player.
-
C.
platformJoined
Indicates that an entity has become a member or user of a particular platform at some point in time.
-
D.
mayRejoin
Indicates that an entity is permitted or eligible to re-enter or rejoin a group, organization, or prior affiliation after having left or been removed.
-
E.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e3ad548190b2c88332f5d919bd |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087cbe7c819085680f3d67ccc978 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.