Triple
T37460252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patchwerk |
E930898
|
entity |
| Predicate | encounterReputation |
P189500
|
FINISHED |
| Object | iconic gear-check boss |
—
|
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: iconic gear-check boss | Statement: [Patchwerk, encounterReputation, iconic gear-check boss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encounterReputation Context triple: [Patchwerk, encounterReputation, iconic gear-check boss]
-
A.
hasReputationAmong
Indicates that an entity is regarded or perceived in a particular way by a specified group or audience.
-
B.
terrainReputation
Indicates how an entity is regarded or perceived based on its performance, behavior, or influence within a particular type of terrain or environmental setting.
-
C.
tacticalReputation
Indicates the perceived level of skill, reliability, or effectiveness an entity has in planning and executing tactics within a given context.
-
D.
reputationInLore
Indicates how an entity is regarded or reputed within a fictional or narrative lore context.
-
E.
refersToPersonReputation
Indicates that something is about, concerns, or makes reference to a particular person's reputation.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 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. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:17 p.m.