Triple
T35917653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mina Clavero – Giulio Cesare |
E1038790
|
entity |
| Predicate | cornerCharacteristics |
P128001
|
FINISHED |
| Object | numerous tight hairpins |
—
|
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: numerous tight hairpins | Statement: [Mina Clavero – Giulio Cesare, cornerCharacteristics, numerous tight hairpins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cornerCharacteristics Context triple: [Mina Clavero – Giulio Cesare, cornerCharacteristics, numerous tight hairpins]
-
A.
ruleCharacteristics
Indicates the defining properties, constraints, or parameters that specify how a particular rule operates or should be applied.
-
B.
entityCharacteristic
chosen
Indicates that an entity possesses, exhibits, or is defined by a particular characteristic or attribute.
-
C.
catalogCharacteristic
Indicates that a catalog has a specific characteristic or attribute associated with it.
-
D.
termCharacteristics
Indicates the defining properties, attributes, or features that characterize a given term.
-
E.
projectCharacteristics
Indicates the defining features, qualities, or attributes that characterize a particular project.
- 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_69f76e2320748190b7f5c4750d0cd0d3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaa7a89081909b1d7b3118c3d4b1 |
completed | May 3, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:07 p.m.