Triple
T21124315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District and Circle |
E520516
|
entity |
| Predicate | hasCollectionGenre |
P124610
|
FINISHED |
| Object | poetry collection |
—
|
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: poetry collection | Statement: [District and Circle, hasCollectionGenre, poetry collection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollectionGenre Context triple: [District and Circle, hasCollectionGenre, poetry collection]
-
A.
includedInGenreCollection
Indicates that something is a member of, or contained within, a specific genre-based collection.
-
B.
hasGenreList
Indicates that an entity is associated with a set or list of genres that categorize or describe it.
-
C.
hasTargetGenreCategory
Indicates that something is associated with or classified under a specific target genre category.
-
D.
hasGenreRelation
chosen
Indicates that there is an association between an entity and a specific genre, specifying the type or category it belongs to.
-
E.
hasUseGenre
Indicates that something (such as a work, product, or item) is associated with or categorized under a particular genre for its use or purpose.
- 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_69e0b50a623881909c0bbaf4f2c055e7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72237c1a4819090987c645114d452 |
completed | April 21, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:56 p.m.