Triple
T35146737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gunn Ancient |
E1014857
|
entity |
| Predicate | belongsToTartanRegisterCategory |
P19933
|
FINISHED |
| Object | clan tartan (Gunn) |
—
|
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: clan tartan (Gunn) | Statement: [Gunn Ancient, belongsToTartanRegisterCategory, clan tartan (Gunn)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToTartanRegisterCategory Context triple: [Gunn Ancient, belongsToTartanRegisterCategory, clan tartan (Gunn)]
-
A.
belongsToCatalogOf
chosen
Indicates that one item is included within, or is a member of, a particular catalog or collection.
-
B.
hasCategoryOn
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
C.
hasRelatedCategory
Indicates that one category is associated with another category through a non-hierarchical, contextually relevant relationship.
-
D.
canBelongTo
Indicates that something is capable of being a member or part of a particular group, category, or owner.
-
E.
containsCategory
Indicates that one entity includes or encompasses a specific category as part of its classification or organizational structure.
- 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_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff80d9a1d88190a95b1488acd6e2e5 |
completed | May 9, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69ff802ae2dc819093a3cda42b63dcbd |
completed | May 9, 2026, 6:42 p.m. |
Created at: May 3, 2026, 4:02 p.m.