Triple
T33047143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juba |
E845626
|
entity |
| Predicate | stageCharacterType |
P70717
|
FINISHED |
| Object | noble lover |
—
|
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: noble lover | Statement: [Juba, stageCharacterType, noble lover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageCharacterType Context triple: [Juba, stageCharacterType, noble lover]
-
A.
stagePersonaOf
chosen
Indicates a relationship where one entity is the staged or performed persona, role, or character representation of another entity.
-
B.
styleCharacter
Indicates that one entity defines, influences, or characterizes the stylistic qualities or manner of expression of another entity.
-
C.
portrayedByCharacterType
Indicates that an entity is depicted or represented by a character of a specified type (e.g., hero, villain, sidekick) in a narrative or media work.
-
D.
theaterRole
Indicates that an entity holds or performs a specific role or character in a theatrical production in relation to another entity (such as a play or performance).
-
E.
actorRole
Indicates that an entity participates in an event or action in a specific capacity or function (such as performer, initiator, or responsible party).
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:24 a.m.