Triple
T23514411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Case of the Perjured Parrot |
E572515
|
entity |
| Predicate | workInLegalFiction |
P152681
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [The Case of the Perjured Parrot, workInLegalFiction, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workInLegalFiction Context triple: [The Case of the Perjured Parrot, workInLegalFiction, yes]
-
A.
legalFiction
Indicates a relationship where something is treated as true or as having a particular legal status or effect, even though it is not literally or factually the case, for the purpose of applying or interpreting the law.
-
B.
workInFiction
Indicates that one entity is a fictional work in which the other entity appears or is set.
-
C.
conductsInFiction
Indicates that an entity carries out or performs an action or role within a fictional context or narrative.
-
D.
worksForInNovel
Indicates that one entity is employed by or serves another entity within the fictional context of a specific novel.
-
E.
scriptInLaw
Indicates that a particular writing system or script is used within the text of a legal document or law.
- 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_69e245b5e4208190bac8a6509867e394 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1aa80d9048190ab735dddd301feb4 |
completed | April 29, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f0bd4a0e408190ad8916faf23562d9 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 17, 2026, 6:08 p.m.