Triple
T35511123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Institute |
E1026286
|
entity |
| Predicate | playerCan |
P82156
|
FINISHED |
| Object | ally with The Institute |
—
|
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: ally with The Institute | Statement: [The Institute, playerCan, ally with The Institute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerCan Context triple: [The Institute, playerCan, ally with The Institute]
-
A.
hasPlayer
Indicates that an entity (such as a team, game, or roster) includes or is associated with a specific player.
-
B.
hasPlayableCharacter
Indicates that an entity includes or is associated with a character that a user can control or play as.
-
C.
allowsPlayerAction
chosen
Indicates that one entity permits or enables a player to perform a specific action within a system or context.
-
D.
controlsPlayerEligibility
Indicates a relationship where one entity determines or regulates whether a player is allowed to participate.
-
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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: May 3, 2026, 4:04 p.m.