Triple
T34463233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benbulben |
E884699
|
entity |
| Predicate | hasLandformShape |
P940
|
FINISHED |
| Object | table mountain |
—
|
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: table mountain | Statement: [Benbulben, hasLandformShape, table mountain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandformShape Context triple: [Benbulben, hasLandformShape, table mountain]
-
A.
hasLandform
chosen
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
-
B.
hasLandformOrigin
Indicates that something originates from, or is formed by, a particular landform.
-
C.
createsLandform
Indicates that one entity brings about the formation or existence of a physical landform in relation to another entity.
-
D.
connectsLandform
Indicates a relationship where one landform serves as a physical link or passage between two or more other landforms.
-
E.
landerType
Indicates the specific kind or category of lander involved in the relationship or action.
- 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_69f349c73a94819094dfcf50d00620b8 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
Created at: May 1, 2026, 2 a.m.