Triple
T30098735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matter of Rome |
E764935
|
entity |
| Predicate | includesCycle |
P166280
|
FINISHED |
| Object | Trojan cycle |
—
|
NE NERFINISHED |
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: Trojan cycle | Statement: [Matter of Rome, includesCycle, Trojan cycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCycle Context triple: [Matter of Rome, includesCycle, Trojan cycle]
-
A.
includedInCycle
Indicates that an entity participates in and is part of a closed loop or recurring sequence within a system or structure.
-
B.
isCyclic
Indicates that a structure, process, or sequence forms a closed loop in which elements or states repeat in a cycle.
-
C.
cycleConsistsOf
chosen
Indicates that a cycle is composed of, or made up from, the specified component elements or segments.
-
D.
followsCycle
Indicates that one entity adheres to or repeats a recurring sequence, pattern, or cycle defined or exemplified by another entity.
-
E.
hasCycleInfrastructure
Indicates that a location or route is equipped with infrastructure designed for cycling, such as bike lanes, paths, or related facilities.
- 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_69f22474e4288190b5f895fe3974aa92 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00512437d48190ad20324968ead5f4 |
completed | May 10, 2026, 9:34 a.m. |
| PD | Predicate disambiguation | batch_6a0050227350819099f41369c3d168be |
completed | May 10, 2026, 9:30 a.m. |
Created at: April 29, 2026, 7:08 p.m.