Triple
T38644894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valkyrie |
E938689
|
entity |
| Predicate | requiresBuilding |
P100
|
FINISHED |
| Object | Armory |
—
|
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: Armory | Statement: [Valkyrie, requiresBuilding, Armory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresBuilding Context triple: [Valkyrie, requiresBuilding, Armory]
-
A.
requiresConfiguration
Indicates that one entity depends on another to be set up or configured before it can function or be used.
-
B.
requires
chosen
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
C.
requiresJudgeToBe
Indicates that a situation, action, or process necessitates the judge to possess or be in a specific state, role, or condition.
-
D.
requiresCall
Indicates that one entity must initiate or receive a phone call or similar direct voice communication with another entity as a necessary condition for some action or state.
-
E.
requiresApplicationOf
Indicates that performing one entity or process depends on actively applying or using another entity, method, or resource.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a01185c46f0819089b4a2ad3c3e2f33 |
completed | May 10, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_6a0117e19e008190870663dd45084416 |
completed | May 10, 2026, 11:42 p.m. |
Created at: May 3, 2026, 4:32 p.m.