Triple
T38644188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vulpera |
E938673
|
entity |
| Predicate | requiresReputationWith |
P203027
|
FINISHED |
| Object | Voldunai |
—
|
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: Voldunai | Statement: [Vulpera, requiresReputationWith, Voldunai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresReputationWith Context triple: [Vulpera, requiresReputationWith, Voldunai]
-
A.
reputationRankRequired
Indicates that a certain minimum reputation rank is required for an entity to access, perform, or qualify for the associated action or resource.
-
B.
haveReputation
Indicates that an entity is recognized or regarded in a certain way by others, reflecting its perceived character, quality, or status.
-
C.
providesReputationWith
Indicates that one entity grants or assigns a reputation value, score, or status to another entity.
-
D.
associatedWithReputation
Indicates a relationship where an entity is linked to, influenced by, or characterized in terms of another entity’s reputation or perceived standing.
-
E.
reputationUsedFor
Indicates that an entity’s reputation is leveraged or applied for a particular purpose, function, or outcome.
- F. None of above. chosen
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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0115fb84448190b8b67a5ace7b289a |
completed | May 10, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_6a0114ef60a081908f8db7868cf29b2f |
completed | May 10, 2026, 11:29 p.m. |
| PDg | Predicate description generation | batch_6a0115fadcec8190bd1be2b44c1fc397 |
completed | May 10, 2026, 11:34 p.m. |
Created at: May 3, 2026, 4:32 p.m.