Triple
T25383380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angel Eyes |
E631451
|
entity |
| Predicate | featuresPoliceOfficerProtagonist |
P21567
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Angel Eyes, featuresPoliceOfficerProtagonist, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresPoliceOfficerProtagonist Context triple: [Angel Eyes, featuresPoliceOfficerProtagonist, true]
-
A.
policeCharacter
Indicates that one entity serves as a police officer or law-enforcement figure in relation to another entity.
-
B.
featuresProtagonistOccupation
chosen
Indicates that the work’s main character has a specified occupation or job role.
-
C.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
D.
protagonistType
Indicates the role or category that the main character (protagonist) of a story or scenario belongs to.
-
E.
policeForceCharacteristic
Indicates that a specified characteristic, quality, or attribute is associated with a particular police force.
- 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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 21, 2026, 1:46 p.m.