Triple
T23387498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PUA-A |
E593923
|
entity |
| Predicate | hasAssignedCharacters |
P58050
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [PUA-A, hasAssignedCharacters, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssignedCharacters Context triple: [PUA-A, hasAssignedCharacters, false]
-
A.
containsAssignedCharacters
chosen
Indicates that an entity includes or holds one or more characters that have been specifically assigned to it.
-
B.
hasOwnerCharacters
Indicates that an entity is associated with one or more characters who own or are responsible for it.
-
C.
hasCharacters
Indicates that an entity (such as a work or story) includes or features certain characters as part of its content.
-
D.
hasHumanCharacters
Indicates that the subject includes or features characters that are human beings.
-
E.
hasHumanCharacterRole
Indicates that an entity is assigned a role or function specifically associated with a human character within a context such as a story, performance, or representation.
- 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a498fd08819085e90a872d9d0c7a |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:35 p.m.