Triple
T36450211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palmar |
E897986
|
entity |
| Predicate | describesSurface |
P62440
|
FINISHED |
| Object | anterior surface 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: anterior surface of the hand | Statement: [Palmar, describesSurface, anterior surface of the hand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesSurface Context triple: [Palmar, describesSurface, anterior surface of the hand]
-
A.
surfaceDescription
chosen
Indicates that one entity provides a textual or qualitative description of the surface characteristics or appearance of another entity.
-
B.
surfaceType
Indicates the kind or classification of surface associated with an entity or interaction.
-
C.
surfaceFeatureOf
Indicates that one entity is a surface-level characteristic, pattern, or feature belonging to or present on another entity.
-
D.
surfaceFeatureKnowledge
Indicates that an entity possesses information or awareness about the characteristics or properties of a surface.
-
E.
surfaceExpressionOf
Indicates that one entity is a specific surface-level manifestation or observable form of another underlying entity or concept.
- 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_69f76e5720b481908f8177ac24a7560b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: May 3, 2026, 4:10 p.m.