Triple
T4017168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kleeblatt |
E91190
|
entity |
| Predicate | symbolReferenced |
P53956
|
FINISHED |
| Object | cloverleaf |
—
|
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: cloverleaf | Statement: [Kleeblatt, symbolReferenced, cloverleaf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolReferenced Context triple: [Kleeblatt, symbolReferenced, cloverleaf]
-
A.
symbolRoot
Indicates a relationship where one symbol serves as the root or base form from which another symbol is derived or structured.
-
B.
symbolText
Indicates that a symbol is associated with or represented by a specific piece of text.
-
C.
symbolType
Indicates the classification or category of a symbol based on its role, form, or function within a given system.
-
D.
isReferencedIn
Indicates that one entity is cited, mentioned, or otherwise referred to within another entity.
-
E.
refersSpecificallyTo
Indicates that one entity makes an explicit, precise reference to another particular entity, distinguishing it from more general or ambiguous references.
- 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaec08dc8190a341809059554f84 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fa6fec81909b1190ecbba61410 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefaea76c48190add2e7cee180e8b1 |
completed | March 9, 2026, 4:52 p.m. |
Created at: March 9, 2026, 3:35 p.m.