Triple
T34797872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Fighters Guild |
E1003136
|
entity |
| Predicate | playerCanBecome |
P64765
|
FINISHED |
| Object | member |
—
|
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: member | Statement: [The Fighters Guild, playerCanBecome, member]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerCanBecome Context triple: [The Fighters Guild, playerCanBecome, member]
-
A.
controlsPlayerEligibility
Indicates a relationship where one entity determines or regulates whether a player is allowed to participate.
-
B.
canGain
Indicates that one entity has the potential or ability to obtain, acquire, or increase something from another entity or source.
-
C.
canJoin
chosen
Indicates that one entity is permitted or able to become a member or participant in another entity or group.
-
D.
couldBePromotedTo
Indicates a potential or eligibility for one entity to be advanced or elevated to a higher role, status, or position relative to another.
-
E.
allowsCandidacyTo
Indicates that one entity grants another entity the right or eligibility to stand as a candidate for a position, role, or office.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 3, 2026, 3:59 p.m.