Triple
T14046714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sully Erna (solo) |
E337973
|
entity |
| Predicate | activeRoleOfSullyErna |
P53708
|
FINISHED |
| Object | singer |
—
|
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: singer | Statement: [Sully Erna (solo), activeRoleOfSullyErna, singer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeRoleOfSullyErna Context triple: [Sully Erna (solo), activeRoleOfSullyErna, singer]
-
A.
roleInSyriana
Indicates that one entity has a specific role or involvement in the context of "Syriana," such as participation, function, or contribution related to it.
-
B.
sonRole
Indicates that one entity holds the role or relationship of a son with respect to another entity.
-
C.
actorRole
chosen
Indicates that an entity participates in an event or action in a specific capacity or function (such as performer, initiator, or responsible party).
-
D.
actingRoleType
Indicates the specific type or category of role an entity performs when acting in a particular capacity or function.
-
E.
eraCharacter
Indicates that a character is associated with, or belongs to, a particular historical or fictional era.
- 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de312df37081909f45ce3e219af5dc |
completed | April 14, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.