Triple
T23894345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revelations |
E600861
|
entity |
| Predicate | hasNotableRoleBy |
P161
|
FINISHED |
| Object | Tamala Jones |
E148183
|
NE 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: Tamala Jones | Statement: [Revelations, hasNotableRoleBy, Tamala Jones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableRoleBy Context triple: [Revelations, hasNotableRoleBy, Tamala Jones]
-
A.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
-
B.
hasRole
chosen
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
C.
hasAuthorRoleFor
Indicates that an entity serves in the role of author for another entity, such as a work, document, or publication.
-
D.
includesRoles
Indicates that one entity contains or encompasses one or more specified roles within its scope or structure.
-
E.
hasNotableOwner
Indicates that an entity is or has been owned by a person or organization considered notable or significant.
- F. None of above.
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_69e295341ac0819080647f2908af793c |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cdd857d081908740c4abb246c2ba |
completed | April 29, 2026, 9:22 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0fe334e06481908a0918de150bc01c |
completed | May 22, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:25 p.m.