Triple
T35009804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Institute (Fallout) |
E1009912
|
entity |
| Predicate | playerCanJoin |
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: [The Institute (Fallout), playerCanJoin, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerCanJoin Context triple: [The Institute (Fallout), playerCanJoin, true]
-
A.
canJoin
chosen
Indicates that one entity is permitted or able to become a member or participant in another entity or group.
-
B.
hasPlayerWhoLaterJoined
Indicates that an entity has a player associated with it who, at some later time, joined another specified entity or group.
-
C.
hasPlayer
Indicates that an entity (such as a team, game, or roster) includes or is associated with a specific player.
-
D.
controlsPlayerEligibility
Indicates a relationship where one entity determines or regulates whether a player is allowed to participate.
-
E.
allowsPlayerAction
Indicates that one entity permits or enables a player to perform a specific action within a system or context.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 3, 2026, 4:01 p.m.