Triple
T20123139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shotwell |
E490661
|
entity |
| Predicate | sceneReputation |
P78940
|
FINISHED |
| Object | lesser-known band |
—
|
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: lesser-known band | Statement: [Shotwell, sceneReputation, lesser-known band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sceneReputation Context triple: [Shotwell, sceneReputation, lesser-known band]
-
A.
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.
-
B.
localReputation
chosen
Indicates the perceived standing, trustworthiness, or esteem an entity holds within a specific local community or area.
-
C.
scopeOfReputation
Indicates the range or extent within which an entity’s reputation is recognized, relevant, or has effect.
-
D.
placeInReputation
Indicates that an entity holds a particular standing, status, or level within a reputation or ranking system.
-
E.
collectionReputation
Indicates the perceived quality, trustworthiness, or status associated with a particular collection based on others’ evaluations or interactions.
- 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6674054188190a15d55a73e86d143 |
completed | April 20, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:30 p.m.