Triple
T27192254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sensing–Intuition |
E683505
|
entity |
| Predicate | hasPole |
P97140
|
FINISHED |
| Object | Sensing |
—
|
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: Sensing | Statement: [Sensing–Intuition, hasPole, Sensing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPole Context triple: [Sensing–Intuition, hasPole, Sensing]
-
A.
hasPoleAt
chosen
Indicates that one entity possesses, contains, or is associated with a pole located at a specific point or position.
-
B.
hasDoublePoleAt
Indicates that a function or expression has a pole of order two (a second-order singularity) at a specified point.
-
C.
hasPit
Indicates that one entity possesses, contains, or is characterized by a pit or hollow space.
-
D.
hasPolarSetting
Indicates that something is configured or oriented according to a polar coordinate or polar reference system.
-
E.
hasPylon
Indicates that one entity possesses, includes, or is equipped with a pylon as part of its structure or configuration.
- 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_69eefad140408190b8586fdebcf9af46 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 27, 2026, 9:32 a.m.