Triple
T35981201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silvertails |
E1040566
|
entity |
| Predicate | appliesToReputation |
P159475
|
FINISHED |
| Object | successful club |
—
|
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: successful club | Statement: [Silvertails, appliesToReputation, successful club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToReputation Context triple: [Silvertails, appliesToReputation, successful club]
-
A.
associatedWithReputation
Indicates a relationship where an entity is linked to, influenced by, or characterized in terms of another entity’s reputation or perceived standing.
-
B.
reputationUsedFor
chosen
Indicates that an entity’s reputation is leveraged or applied for a particular purpose, function, or outcome.
-
C.
denotesReputationOf
Indicates that one entity represents, expresses, or serves as an indicator of the reputation or perceived standing of another entity.
-
D.
haveReputation
Indicates that an entity is recognized or regarded in a certain way by others, reflecting its perceived character, quality, or status.
-
E.
providesReputationWith
Indicates that one entity grants or assigns a reputation value, score, or status to another entity.
- 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff53389a0481908b2baeb43c6294f0 |
completed | May 9, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69ff52e2b4b88190b38d160d771fe14b |
completed | May 9, 2026, 3:29 p.m. |
Created at: May 3, 2026, 4:07 p.m.