Triple
T29779010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhodopis |
E755457
|
entity |
| Predicate | centralCharacterStatus |
P52203
|
FINISHED |
| Object | slaveGirl |
—
|
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: slaveGirl | Statement: [Rhodopis, centralCharacterStatus, slaveGirl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralCharacterStatus Context triple: [Rhodopis, centralCharacterStatus, slaveGirl]
-
A.
leadCharacterStatus
Indicates the role or condition of an entity when it serves as the primary or central character in a narrative or context.
-
B.
characterStatusInStory
chosen
Indicates the role or condition a character holds within the context of a specific story or narrative.
-
C.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
-
D.
featuresCharacterWithStatus
Indicates that something (such as a work or scene) includes a character who has a specified status or condition.
-
E.
titleCharacterState
Indicates the state or condition a character is in within the context of a specific title or work.
- 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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 28, 2026, 8:48 p.m.