Triple
T29010409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chiarina |
E736547
|
entity |
| Predicate | cycleConsistsOf |
P166280
|
FINISHED |
| Object | short character pieces |
—
|
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: short character pieces | Statement: [Chiarina, cycleConsistsOf, short character pieces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cycleConsistsOf Context triple: [Chiarina, cycleConsistsOf, short character pieces]
-
A.
cycleWith
Indicates that two or more entities participate together in a cycling activity, such as riding bicycles along the same route or at the same time.
-
B.
cycleStructure
Indicates the arrangement and connections of elements within a repeating or cyclical pattern, specifying how components are ordered and linked in a cycle.
-
C.
cycleBy
Indicates that one entity moves or travels by means of riding a bicycle (or similar cycle) in relation to another entity or context.
-
D.
cycleType
Indicates the specific kind or category of cycle involved in a repeated or cyclical process or relationship.
-
E.
followsCycle
Indicates that one entity adheres to or repeats a recurring sequence, pattern, or cycle defined or exemplified by 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 9:41 a.m.