Triple
T38588916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotface |
E932407
|
entity |
| Predicate | requiresGroup |
P69867
|
FINISHED |
| Object | raid group |
—
|
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: raid group | Statement: [Rotface, requiresGroup, raid group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresGroup Context triple: [Rotface, requiresGroup, raid group]
-
A.
requiresGroupContent
Indicates that an entity depends on or mandates the presence of content associated with a specific group in order to be valid, complete, or functional.
-
B.
requiresMember
Indicates that one entity depends on or mandates the participation, presence, or inclusion of another entity as a member in order for a condition, action, or relationship to hold.
-
C.
usesGroup
chosen
Indicates that an entity makes use of, operates with, or relies on a particular group as a collective resource, tool, or participant in some activity or process.
-
D.
guardedByGroup
Indicates that an entity is protected or watched over by a group acting as its guards.
-
E.
requiredTo
Indicates that one entity has an obligation or necessity to perform an action or satisfy a condition in relation to another entity 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00bc079314819096271bba60bee52d |
completed | May 10, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_6a00bba5bd408190ace5db0c4a90dc6f |
completed | May 10, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4:32 p.m.