Triple
T20054029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonnet 144 |
E499281
|
entity |
| Predicate | hasCoupletFunction |
P138525
|
FINISHED |
| Object | moral reflection |
—
|
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: moral reflection | Statement: [Sonnet 144, hasCoupletFunction, moral reflection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoupletFunction Context triple: [Sonnet 144, hasCoupletFunction, moral reflection]
-
A.
hasCoupling
Indicates that two entities are linked or joined together in a way that allows them to interact, transfer, or coordinate motion, energy, or information.
-
B.
hasCouplingConstant
Indicates that one entity is associated with a specific coupling constant value that quantifies the strength of an interaction or relationship.
-
C.
hasCouplers
Indicates that one entity is equipped with or possesses couplers that enable it to connect or link to another entity.
-
D.
hasConjunction
Indicates that two or more entities are linked together by a coordinating conjunction, forming a combined or joint relationship.
-
E.
hasChainFunction
Indicates that an entity possesses or is associated with a specific function or role within a chain or sequence of operations.
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66331c7488190840d43792ff09977 |
completed | April 20, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:38 p.m.