Triple
T34797663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dunmer |
E1003132
|
entity |
| Predicate | creatureAssociation |
P51902
|
FINISHED |
| Object | guar |
—
|
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: guar | Statement: [Dunmer, creatureAssociation, guar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creatureAssociation Context triple: [Dunmer, creatureAssociation, guar]
-
A.
speciesAssociatedWith
Indicates that there is a relevant connection or linkage between a species and another entity (such as a habitat, condition, or feature), without specifying the exact nature of that relationship.
-
B.
animalAssociation
Indicates a relationship in which one animal is associated with another animal or entity, such as through interaction, co-occurrence, or ecological linkage.
-
C.
associatedWithAnimal
chosen
Indicates a relationship where an entity has a connection, link, or relevance to an animal.
-
D.
associationWithHumans
Indicates a general relationship, connection, or involvement between an entity and one or more humans.
-
E.
associatedBeings
Indicates that two or more beings are linked or connected to each other in some relevant way.
- 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_69ff59b33a38819086cc9aa19b81748b |
completed | May 9, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69ff587758f88190a39c2164341dc554 |
completed | May 9, 2026, 3:53 p.m. |
Created at: May 3, 2026, 3:59 p.m.