Triple
T34016734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nyuto Onsen |
E872266
|
entity |
| Predicate | healingReputationFor |
P178155
|
FINISHED |
| Object | neuralgia |
—
|
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: neuralgia | Statement: [Nyuto Onsen, healingReputationFor, neuralgia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: healingReputationFor Context triple: [Nyuto Onsen, healingReputationFor, neuralgia]
-
A.
placeInReputation
Indicates that an entity holds a particular standing, status, or level within a reputation or ranking system.
-
B.
reputationEffect
Indicates how one entity’s actions or characteristics influence the perceived reputation or standing of another entity.
-
C.
handlingReputation
Indicates that one entity manages, influences, or is responsible for maintaining the reputation or public perception of another entity.
-
D.
reputationUsedFor
Indicates that an entity’s reputation is leveraged or applied for a particular purpose, function, or outcome.
-
E.
reputationBuiltFor
Indicates that one entity has established or developed a reputation specifically for or in relation to 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70c53062c8190b4cb7be22ab00bc7 |
completed | May 3, 2026, 8:50 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70b94784c8190970d654e066eb50d |
completed | May 3, 2026, 8:47 a.m. |
Created at: May 1, 2026, 1:51 a.m.