Triple
T21943730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pondicherry Zoo |
E541884
|
entity |
| Predicate | hasGenreOfWorkItAppearsIn |
P146635
|
FINISHED |
| Object | philosophical novel |
—
|
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: philosophical novel | Statement: [Pondicherry Zoo, hasGenreOfWorkItAppearsIn, philosophical novel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenreOfWorkItAppearsIn Context triple: [Pondicherry Zoo, hasGenreOfWorkItAppearsIn, philosophical novel]
-
A.
belongsToWorkGenre
Indicates that a creative work is classified under or associated with a particular genre.
-
B.
seriesGenreOfNotableWork
Indicates that a particular genre characterizes the notable work associated with a series.
-
C.
hasWorkInGenreOfAuthor
Indicates that a work is associated with an author whose typical or primary genre matches the genre of that work.
-
D.
notableWorkGenre
Indicates that a particular work is recognized as notable for an entity and specifies the genre to which that work belongs.
-
E.
hasGenreInRoles
Indicates that an entity participates in roles associated with a particular genre or set of genres.
- 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_69e0c47e2e5c81909a7f74ce3de50911 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1242515ec8190b015bf8c7b13be85 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
| PDg | Predicate description generation | batch_69e6fb6991948190a428c3c3bfd1c3b8 |
completed | April 21, 2026, 4:22 a.m. |
Created at: April 16, 2026, 7:56 p.m.