Triple
T4361373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spenserian stanza |
E98668
|
entity |
| Predicate | hasMeterPattern |
P8151
|
FINISHED |
| Object | first eight lines in iambic pentameter |
—
|
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: first eight lines in iambic pentameter | Statement: [Spenserian stanza, hasMeterPattern, first eight lines in iambic pentameter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeterPattern Context triple: [Spenserian stanza, hasMeterPattern, first eight lines in iambic pentameter]
-
A.
hasMeter
Indicates that one entity possesses, uses, or is associated with a specific meter (a measuring device or metrical pattern).
-
B.
hasBearingPattern
Indicates a relationship where an object or system exhibits or is characterized by a specific bearing arrangement or configuration pattern.
-
C.
hasPattern
chosen
Indicates that one entity exhibits, follows, or is characterized by a specific recurring form, structure, or design defined by another entity.
-
D.
hasMetricType
Indicates that something is associated with or characterized by a specific type or category of metric.
-
E.
hasBuildingPattern
Indicates that an entity exhibits or follows a particular architectural or structural building pattern.
- 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351e47d388190b31500189577cd75 |
completed | March 12, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:16 p.m.