Triple
T16336684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady of Driftmark |
E396695
|
entity |
| Predicate | heldByCharacterType |
P123007
|
FINISHED |
| Object | princess |
—
|
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: princess | Statement: [Lady of Driftmark, heldByCharacterType, princess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldByCharacterType Context triple: [Lady of Driftmark, heldByCharacterType, princess]
-
A.
performedByCharacterType
Indicates that an action or event is carried out by a character belonging to a specified character type or category.
-
B.
usedByCharacter
Indicates that something (such as an item, ability, or resource) is utilized or employed by a particular character.
-
C.
typeOfCharacter
Indicates that one entity is a specific kind or category of character in relation to another entity.
-
D.
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.
-
E.
supportedByCharacter
Indicates that an entity receives backing, assistance, or endorsement from a specific character.
- F. None of above. chosen
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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4e524448190870a6ef569017b56 |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:07 a.m.