Triple
T18618953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | habesha kemis |
E455099
|
entity |
| Predicate | borderPlacement |
P94290
|
FINISHED |
| Object | hem |
—
|
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: hem | Statement: [habesha kemis, borderPlacement, hem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderPlacement Context triple: [habesha kemis, borderPlacement, hem]
-
A.
buttonPlacement
Indicates the spatial or positional arrangement of a button relative to other elements or within a given interface or context.
-
B.
borderPoint
Indicates a point that lies on the boundary between two regions or entities.
-
C.
borderDistribution
chosen
Indicates how a boundary or border is spatially arranged, divided, or allocated between adjacent entities.
-
D.
placementType
Indicates the specific manner or category in which something is positioned, arranged, or assigned within a given context.
-
E.
borderArea
Indicates that an area lies along or near the boundary between two regions, countries, or territories.
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54d07dc288190bb3b8b5ab06518da |
completed | April 19, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.