Triple
T37551689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Howling Fjord |
E933603
|
entity |
| Predicate | majorAllianceHub |
P49430
|
FINISHED |
| Object | Valgarde |
—
|
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: Valgarde | Statement: [Howling Fjord, majorAllianceHub, Valgarde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorAllianceHub Context triple: [Howling Fjord, majorAllianceHub, Valgarde]
-
A.
allianceHubFor
chosen
Indicates that one entity serves as a central coordinating hub or focal point for an alliance involving another entity.
-
B.
allianceProject
Indicates a collaborative project or initiative jointly undertaken by allied entities within an alliance relationship.
-
C.
allianceScope
Indicates the extent or boundaries of cooperation and mutual obligations defined within an alliance relationship.
-
D.
allianceStructure
Indicates the organizational or relational configuration that defines how members of an alliance are structured and interconnected.
-
E.
alliancesAround
Indicates that alliances are formed or exist in the vicinity or context of a specified entity or focal point.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a000a1d8fa88190a1d82ac746565c48 |
completed | May 10, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_6a0008b26eb88190ae03b2309a614774 |
completed | May 10, 2026, 4:25 a.m. |
Created at: May 3, 2026, 4:17 p.m.