Triple
T4584628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garter star |
E101937
|
entity |
| Predicate | locationShownOn |
P8908
|
FINISHED |
| Object | left side of court dress |
—
|
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: left side of court dress | Statement: [Garter star, locationShownOn, left side of court dress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationShownOn Context triple: [Garter star, locationShownOn, left side of court dress]
-
A.
location depicted
chosen
Indicates that one entity visually represents or shows the place where another entity is situated or occurs.
-
B.
locationFocus
Indicates that the primary or most relevant location associated with an entity, event, or relation is being specified or emphasized.
-
C.
locatedAlong
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
-
D.
locationFormed
Indicates the place or geographic area where an entity (such as an organization, group, or structure) was originally established or came into existence.
-
E.
subjectLocation
Indicates that one entity is located at, in, or near the place or position specified 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_69bd43d4ce208190b53158c882b222e3 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59056bb48190ba1e0b5beda9bdc4 |
completed | March 20, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69bd522acbcc8190bf24d9517793a2c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.