Triple
T37225141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Droopy |
E922985
|
entity |
| Predicate | employerInSomeCartoons |
P40735
|
FINISHED |
| Object | police department |
—
|
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: police department | Statement: [Droopy, employerInSomeCartoons, police department]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employerInSomeCartoons Context triple: [Droopy, employerInSomeCartoons, police department]
-
A.
employerInPlot
Indicates that one entity serves as the employer of another within the context of a specific plot or storyline.
-
B.
employerInUniverse
chosen
Indicates that one entity serves as the employer of another within a specified universe, context, or world.
-
C.
employerInReality
Indicates that one entity is the actual, real-world employer of another entity, as opposed to a nominal, legal, or assumed employer.
-
D.
developerOfWorkAppearingIn
Indicates that one entity is the creator or developer of a work in which another entity appears or is featured.
-
E.
employerOfCreator
Indicates that one entity is the employer of the entity that created another entity.
- 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_69f76ea7f0008190b31b8e30f3d05a71 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 3, 2026, 4:15 p.m.