Triple
T20979052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | canto |
E516701
|
entity |
| Predicate | hasLevelOfDivision |
P275
|
FINISHED |
| Object | higher than stanza |
—
|
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: higher than stanza | Statement: [canto, hasLevelOfDivision, higher than stanza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLevelOfDivision Context triple: [canto, hasLevelOfDivision, higher than stanza]
-
A.
hasDivisionLevel
chosen
Indicates that one entity is associated with a specific hierarchical or organizational division level of another entity.
-
B.
hasNoFurtherSubdivisionLevel
Indicates that the referenced entity is at the lowest level of subdivision and cannot be further subdivided into smaller units within the given hierarchy.
-
C.
hasNumberOfDivisions
Indicates the relationship that specifies how many divisions or subunits an entity possesses.
-
D.
hasDivisionNames
Indicates that an entity is associated with one or more names of its internal divisions or subunits.
-
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_69e0b4fee5ac8190875fa9ceba1a5e5e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fbdc6ca08190919717f4328c7a0d |
completed | April 21, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:47 p.m.