Triple
T21555343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morning Has Broken |
E531875
|
entity |
| Predicate | hasMeterType |
P4875
|
FINISHED |
| Object | hymn meter |
—
|
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: hymn meter | Statement: [Morning Has Broken, hasMeterType, hymn meter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeterType Context triple: [Morning Has Broken, hasMeterType, hymn meter]
-
A.
hasMeter
chosen
Indicates that one entity possesses, uses, or is associated with a specific meter (a measuring device or metrical pattern).
-
B.
hasMetricType
Indicates that something is associated with or characterized by a specific type or category of metric.
-
C.
hasMeasurement
Indicates that an entity is associated with a specific measured value, often including a unit or measurement context.
-
D.
metricType
Indicates the specific category or kind of measurement that a given metric represents.
-
E.
hasMeasurementRole
Indicates that an entity participates in a measurement activity in a specific functional role (e.g., as the measurer, instrument, or measured subject).
- 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eed2df48c88190894b6b08a5cb6390 |
completed | April 27, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:29 p.m.