Triple
T34672238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4R |
E890405
|
entity |
| Predicate | hasMeaningOfSideDesignator |
P144222
|
FINISHED |
| Object | right |
—
|
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: right | Statement: [4R, hasMeaningOfSideDesignator, right]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeaningOfSideDesignator Context triple: [4R, hasMeaningOfSideDesignator, right]
-
A.
hasLeftSideDesignation
Indicates that a specific designation, label, or marker is assigned to the left side of an object, structure, or spatial arrangement.
-
B.
hasDesignSide
Indicates that one entity is located on, associated with, or corresponds to a particular side or face of another entity’s design.
-
C.
hasDesignationMeaning
chosen
Indicates that one designation, label, or title conveys or corresponds to a particular meaning or semantic interpretation.
-
D.
sideDesignation
Indicates how an entity is classified or labeled with respect to a particular side, position, or alignment within a relationship or context.
-
E.
hasASideOf
Indicates that one entity possesses or includes a particular side or face as part of its structure or boundary.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff1d85441c8190931e758685a269f7 |
completed | May 9, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_69ff1d186cc48190b315c61e23de6551 |
completed | May 9, 2026, 11:40 a.m. |
Created at: May 1, 2026, 2:05 a.m.