Triple
T27037010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L’Olive |
E681081
|
entity |
| Predicate | formStructure |
P172109
|
FINISHED |
| Object | ordered sequence rather than isolated sonnets |
—
|
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: ordered sequence rather than isolated sonnets | Statement: [L’Olive, formStructure, ordered sequence rather than isolated sonnets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formStructure Context triple: [L’Olive, formStructure, ordered sequence rather than isolated sonnets]
-
A.
formFunction
Indicates that one entity’s physical form, structure, or configuration determines or enables the function or role performed by another (or by itself).
-
B.
formsFusionWith
Indicates that two or more entities combine to create a single, unified entity or structure.
-
C.
formsEntity
Indicates that one entity creates, shapes, or constitutes another entity as a result or outcome.
-
D.
formsFrom
Indicates that one entity is created, derived, or takes shape as a result of another entity.
-
E.
formsFor
Indicates that one entity constitutes the physical or structural makeup of another entity.
- F. None of above. chosen
Provenance (4 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8de0b948190ae333e9cd99cbf6c |
completed | May 3, 2026, 1:46 a.m. |
Created at: April 27, 2026, 7:16 a.m.