Triple
T35011406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orsimer |
E1009946
|
entity |
| Predicate | reputationInLore |
P181999
|
FINISHED |
| Object | fierce warriors |
—
|
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: fierce warriors | Statement: [Orsimer, reputationInLore, fierce warriors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reputationInLore Context triple: [Orsimer, reputationInLore, fierce warriors]
-
A.
mythicReputation
Indicates a reputation or renown of legendary, larger-than-life status associated with an entity.
-
B.
laterReputation
Indicates that an entity’s reputation or status at a later time is being referred to in relation to an earlier point or context.
-
C.
refersToPersonReputation
Indicates that something is about, concerns, or makes reference to a particular person's reputation.
-
D.
placeInReputation
Indicates that an entity holds a particular standing, status, or level within a reputation or ranking system.
-
E.
reputationEffect
Indicates how one entity’s actions or characteristics influence the perceived reputation or standing of another entity.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7865578d48190bf90e470634fd97d |
completed | May 3, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f78575917481909a3defd6a4c366bd |
completed | May 3, 2026, 5:27 p.m. |
Created at: May 3, 2026, 4:01 p.m.