Triple
T23235628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poésies lyriques |
E581282
|
entity |
| Predicate | metricCharacteristics |
P128001
|
FINISHED |
| Object | regular versification |
—
|
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: regular versification | Statement: [Poésies lyriques, metricCharacteristics, regular versification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metricCharacteristics Context triple: [Poésies lyriques, metricCharacteristics, regular versification]
-
A.
dataCharacteristic
Indicates that one entity specifies a property, attribute, or feature that characterizes a given piece of data.
-
B.
ruleCharacteristics
Indicates the defining properties, constraints, or parameters that specify how a particular rule operates or should be applied.
-
C.
entityCharacteristic
chosen
Indicates that an entity possesses, exhibits, or is defined by a particular characteristic or attribute.
-
D.
managementCharacteristic
Indicates a defining quality, style, or attribute associated with how something is managed or administered.
-
E.
codeCharacteristic
Indicates that one piece of code possesses a specific property, feature, or quality in relation to another referenced aspect.
- 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_69e2460556f88190be1744a84a84173f |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f192e8c7548190b53434eeb2620a6e |
completed | April 29, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:09 p.m.