Triple
T15340225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacLeod tartan |
E366772
|
entity |
| Predicate | hasPatternElement |
P8151
|
FINISHED |
| Object | repeating sett |
—
|
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: repeating sett | Statement: [MacLeod tartan, hasPatternElement, repeating sett]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPatternElement Context triple: [MacLeod tartan, hasPatternElement, repeating sett]
-
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.
hasUsePattern
Indicates a characteristic or recurring way in which something is typically used or applied.
-
C.
hasElementType
Indicates that something is composed of or contains elements that are of a specified type.
-
D.
hasFormatElement
Indicates that one entity includes, is composed of, or is associated with a specific structural or formatting component of its overall format.
-
E.
hasMetapattern
Indicates that one entity is associated with, characterized by, or governed by a higher-level structural pattern or schema represented by another entity.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e12eb7c8190944a260aa1aa9156 |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:17 a.m.