Triple
T7305911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Wyatt |
E167973
|
entity |
| Predicate | usedMetre |
P4875
|
FINISHED |
| Object | 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: iambic pentameter | Statement: [Thomas Wyatt, usedMetre, iambic pentameter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedMetre Context triple: [Thomas Wyatt, usedMetre, iambic pentameter]
-
A.
usesMetric
Indicates that one entity adopts, applies, or relies on a particular metric or measurement standard in its operation, evaluation, or description.
-
B.
metre
Indicates a measurement relationship where one entity’s length, distance, or size is quantified in units of metres.
-
C.
usedOver
Indicates that one entity has been utilized, applied, or consumed in relation to another entity, typically as a resource, medium, or tool in a particular context or period.
-
D.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
E.
hasMeter
chosen
Indicates that one entity possesses, uses, or is associated with a specific meter (a measuring device or metrical 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_69c6888c820881909fc68f689fe1c251 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebd7dcf88190b3e66bea327fc63d |
completed | March 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:01 p.m.