Triple
T38643945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Void Elves |
E938669
|
entity |
| Predicate | requiresExpansionToUnlock |
P203019
|
FINISHED |
| Object | Legion |
—
|
NE NERFINISHED |
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: Legion | Statement: [Void Elves, requiresExpansionToUnlock, Legion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresExpansionToUnlock Context triple: [Void Elves, requiresExpansionToUnlock, Legion]
-
A.
requiresExpansion
Indicates that something is currently insufficient in scope, detail, or capacity and needs to be broadened, elaborated, or increased.
-
B.
hasExpansion
Indicates that one entity serves as a larger, extended, or elaborated form of another entity.
-
C.
requiresUnlock
Indicates that access to or use of something is contingent on it first being unlocked or otherwise made available.
-
D.
restrictedExpansionOf
Indicates a relationship where one entity is an expansion of another, but with added constraints or limitations that make it more specific or narrowly applicable than the original.
-
E.
expansionPack
Indicates that one item serves as an add-on or supplementary content package that extends the features or scope of another item.
- F. None of above. chosen
Provenance (4 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00dc330b148190aaae2ac6a5327960 |
completed | May 10, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_6a00d9d2904881909dafbfe7b9e5ad81 |
completed | May 10, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_6a00dc3268248190a723e1b7b29f9cda |
completed | May 10, 2026, 7:27 p.m. |
Created at: May 3, 2026, 4:32 p.m.