Triple
T30036140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalkaska sand |
E763162
|
entity |
| Predicate | hasHorizon |
P185954
|
FINISHED |
| Object | A horizon |
—
|
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: A horizon | Statement: [Kalkaska sand, hasHorizon, A horizon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHorizon Context triple: [Kalkaska sand, hasHorizon, A horizon]
-
A.
hasEventHorizon
Indicates that an object possesses an event horizon, a boundary beyond which events cannot affect an outside observer.
-
B.
typicalHorizon
Indicates the usual or characteristic boundary or limit within which something is expected to occur or be observed.
-
C.
horizonStructure
Indicates the structural or organizational characteristics that define how a horizon or boundary layer is formed, arranged, or composed.
-
D.
associatedWithHorizon
Indicates a relationship in which something is linked or connected to a horizon, boundary, or limiting context.
-
E.
eventHorizonType
Indicates the specific kind or classification of an event horizon associated with a given object or phenomenon.
- 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_69f2246fb2b88190acff36bf7975c8f0 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: April 29, 2026, 6:51 p.m.