Triple
T32449179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daphnis |
E829230
|
entity |
| Predicate | ringInteraction |
P174190
|
FINISHED |
| Object | creates vertical structures in ring edges |
—
|
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: creates vertical structures in ring edges | Statement: [Daphnis, ringInteraction, creates vertical structures in ring edges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ringInteraction Context triple: [Daphnis, ringInteraction, creates vertical structures in ring edges]
-
A.
ringPresentedBy
Indicates that one entity has given or formally presented a ring to another entity.
-
B.
ringDiscoveryPrecedes
Indicates that the discovery of a ring occurs earlier in time than another specified event or discovery.
-
C.
ringHistory
Indicates that there is a recorded sequence of past ringing-related events or states associated with an entity.
-
D.
ringPresentationReason
Indicates the reason or occasion for which a ring is being presented or given.
-
E.
branchInteraction
Indicates an interaction or relationship occurring between different branches or subdivisions of an entity, such as communication, coordination, or influence among them.
- 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2e822a88190a7b32d03127a2025 |
completed | May 3, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69f6ba700a708190ab6db62791e43774 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bbbe23d48190b2aa662d69b41900 |
completed | May 3, 2026, 3:06 a.m. |
Created at: May 1, 2026, 12:56 a.m.