Triple
T36450233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palmar |
E897986
|
entity |
| Predicate | oppositeSurfaceOf |
P194337
|
FINISHED |
| Object | back of the hand |
—
|
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: back of the hand | Statement: [Palmar, oppositeSurfaceOf, back of the hand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oppositeSurfaceOf Context triple: [Palmar, oppositeSurfaceOf, back of the hand]
-
A.
outerSurface
Indicates that one entity forms the external boundary or outermost layer of another entity.
-
B.
secondarySurface
Indicates a relationship where one surface functions as a secondary or subordinate surface in relation to a primary or main surface.
-
C.
laterSurface
Indicates that one surface or layer occurs or appears at a later time than another surface or layer in a sequence or process.
-
D.
formerSurface
Indicates that one entity previously served as the surface or outer layer of another entity, but no longer does so.
-
E.
hasAlternativeSurface
Indicates that one entity serves as a different or substitute surface option for another entity.
- F. None of above. chosen
Provenance (4 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_69f76e5720b481908f8177ac24a7560b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
| PDg | Predicate description generation | batch_69fd6a1a38f081908c573aee4696de4f |
completed | May 8, 2026, 4:44 a.m. |
Created at: May 3, 2026, 4:10 p.m.