Triple
T25332943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | kawrchei |
E635199
|
entity |
| Predicate | hasPatternCharacteristic |
P8151
|
FINISHED |
| Object | geometric patterns |
—
|
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: geometric patterns | Statement: [kawrchei, hasPatternCharacteristic, geometric patterns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPatternCharacteristic Context triple: [kawrchei, hasPatternCharacteristic, geometric patterns]
-
A.
hasPattern
chosen
Indicates that one entity exhibits, follows, or is characterized by a specific recurring form, structure, or design defined by another entity.
-
B.
hasPeripheralPattern
Indicates that one entity exhibits or is characterized by a pattern located at or toward the periphery or outer boundary of another entity.
-
C.
hasCharacteristic
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
-
D.
hasRuleCharacteristic
Indicates that something possesses a specific property, feature, or attribute related to a rule or set of rules.
-
E.
hasUsePattern
Indicates a characteristic or recurring way in which something is typically used or applied.
- 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 21, 2026, 1:30 p.m.