Triple
T21563922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assassin |
E532112
|
entity |
| Predicate | hasCollaborativeReputation |
P93104
|
FINISHED |
| Object | sought-after guest vocalist |
—
|
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: sought-after guest vocalist | Statement: [Assassin, hasCollaborativeReputation, sought-after guest vocalist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollaborativeReputation Context triple: [Assassin, hasCollaborativeReputation, sought-after guest vocalist]
-
A.
haveReputation
chosen
Indicates that an entity is recognized or regarded in a certain way by others, reflecting its perceived character, quality, or status.
-
B.
isCollaborative
Indicates that two or more entities work together jointly toward a shared goal or outcome.
-
C.
tributeAssessmentReputation
Indicates the evaluation of an entity’s reputation specifically in the context of determining or justifying a tribute assessment.
-
D.
hasReputationAmong
Indicates that an entity is regarded or perceived in a particular way by a specified group or audience.
-
E.
isCollaboration
Indicates that two or more entities are jointly working together toward a shared goal or producing something in partnership.
- 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eed2e6c19c81909eaae408d94f0625 |
completed | April 27, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:30 p.m.