Triple
T25872330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great kilt |
E651791
|
entity |
| Predicate | upperSectionCanBe |
P145520
|
FINISHED |
| Object | draped over shoulder |
—
|
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: draped over shoulder | Statement: [Great kilt, upperSectionCanBe, draped over shoulder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperSectionCanBe Context triple: [Great kilt, upperSectionCanBe, draped over shoulder]
-
A.
upperSectionType
Indicates the type or category assigned to the upper section or upper part of an object, structure, or entity.
-
B.
upperCourseOf
Indicates that one watercourse represents the upstream or higher-elevation segment of another watercourse within the same river system.
-
C.
upperComponent
Indicates that one component is positioned above or on top of another component within a larger structure or assembly.
-
D.
upperMaterialOption
chosen
Indicates that an entity offers a particular material choice for the upper part of an item (e.g., a product’s upper section).
-
E.
hasUpperPartFrom
Indicates that an entity includes, incorporates, or is composed of an upper part originating from 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_69e7ab3ad9d88190841ddcb93ab02e96 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f602dd86dc8190b36335017d158398 |
completed | May 2, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69f4939148dc81908706cec7d85291bc |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 8:11 a.m.