Triple
T38585373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frostfire Ridge |
E932333
|
entity |
| Predicate | notableFactionPresence |
P17876
|
FINISHED |
| Object | Frostwolf Orcs |
E932342
|
NE 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: Frostwolf Orcs | Statement: [Frostfire Ridge, notableFactionPresence, Frostwolf Orcs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFactionPresence Context triple: [Frostfire Ridge, notableFactionPresence, Frostwolf Orcs]
-
A.
notableForce
Indicates that an entity is recognized as a significant or influential force affecting another entity, system, or context.
-
B.
hasFaction
Indicates that an entity is affiliated with, belongs to, or is represented by a particular faction or group.
-
C.
hasMajorFaction
chosen
Indicates that an entity possesses or is associated with a primary or dominant faction within a given context.
-
D.
portraysFaction
Indicates that one entity depicts, represents, or characterizes a particular faction or group, typically in a narrative, artistic, or media context.
-
E.
notableCharacterAffiliation
Indicates that a notable character is formally associated with, aligned to, or a member of a particular group, organization, or affiliation.
- F. None of above.
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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41ea9c8ccc819090eadfc322c540d4 |
completed | June 29, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.