Triple
T22632610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greek Anthology |
E558590
|
entity |
| Predicate | hasCanonicalDivision |
P1905
|
FINISHED |
| Object | 16 books |
—
|
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: 16 books | Statement: [Greek Anthology, hasCanonicalDivision, 16 books]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonicalDivision Context triple: [Greek Anthology, hasCanonicalDivision, 16 books]
-
A.
hasDivisionRule
Indicates that one entity is governed, organized, or separated according to a specified rule or method of division defined by another entity.
-
B.
hasNumberOfDivisions
chosen
Indicates the relationship that specifies how many divisions or subunits an entity possesses.
-
C.
canonicalDivision
Indicates that one entity is the standard or officially recognized subdivision or partition of another entity.
-
D.
hasCanonicalAspect
Indicates that an entity is associated with its standard or officially recognized aspect, form, or representation.
-
E.
containsDivision
Indicates that one entity includes or encompasses a subdivision or internal division of 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_69e245467d9881908d6985bd0db7a1f1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1700ab4308190a16b0a1b2a0210fd |
completed | April 29, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 3:02 p.m.