Triple
T29098351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | planet Ixchel |
E735069
|
entity |
| Predicate | perceptionModeOfInhabitants |
P164151
|
FINISHED |
| Object | tactile perception |
—
|
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: tactile perception | Statement: [planet Ixchel, perceptionModeOfInhabitants, tactile perception]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perceptionModeOfInhabitants Context triple: [planet Ixchel, perceptionModeOfInhabitants, tactile perception]
-
A.
perceptionByHumans
Indicates that something is perceived, sensed, or experienced through human sensory or cognitive processes.
-
B.
typicalPerception
chosen
Indicates the usual or most common way an entity is perceived or experienced through the senses.
-
C.
fateOfInhabitants
Indicates the outcome or destiny that befalls the inhabitants of a place or group, such as survival, displacement, or death.
-
D.
hasPerception
Indicates that one entity is aware of, senses, or recognizes another entity or phenomenon.
-
E.
publicPerception
Indicates how an individual, group, or entity is viewed, judged, or regarded by the general public or society at large.
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 11:10 a.m.