Triple
T38095700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | brekekekex koax koax |
E951237
|
entity |
| Predicate | meterOrForm |
P142894
|
FINISHED |
| Object | lyric chorus |
—
|
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: lyric chorus | Statement: [brekekekex koax koax, meterOrForm, lyric chorus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meterOrForm Context triple: [brekekekex koax koax, meterOrForm, lyric chorus]
-
A.
meterForm
chosen
Indicates that one entity is the specific metrical pattern or verse form in which another entity (such as a poem or song) is composed.
-
B.
meter
Indicates a measurement relationship where one entity quantifies the length, distance, or extent of another in meters.
-
C.
metricForm
Indicates that one entity is expressed or represented in a particular metric form or measurement format relative to another.
-
D.
meterSystem
Indicates that one entity uses, is measured in, or is associated with a particular system of meters or measurement units.
-
E.
metrizes
Indicates that a given metric defines or induces the topology or structure on a space, making that metric compatible with and fully characterizing the space’s topological properties.
- 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.