Triple
T34797551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nords |
E1003131
|
entity |
| Predicate | culturalEnemy |
P117167
|
FINISHED |
| Object | elves |
—
|
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: elves | Statement: [Nords, culturalEnemy, elves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culturalEnemy Context triple: [Nords, culturalEnemy, elves]
-
A.
opposingCulture
chosen
Indicates a relationship where one culture stands in opposition to, conflicts with, or resists the values, practices, or influence of another culture.
-
B.
archenemyOf
Indicates a relationship in which one entity is the principal or most important enemy of another, often characterized by deep, ongoing opposition or rivalry.
-
C.
combatantCulture
Indicates the cultural background or tradition associated with a participant engaged in a conflict or combat situation.
-
D.
combatantCulture1
Indicates that the first combatant in a conflict is associated with a particular culture or cultural group.
-
E.
combatantCulture2
Indicates the cultural or ethnic background of the second party involved in a combat or conflict relationship.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 3:59 p.m.