Triple
T6651894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paps of Jura |
E150840
|
entity |
| Predicate | prominenceIn |
P42578
|
FINISHED |
| Object | Hebridean landscape |
—
|
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: Hebridean landscape | Statement: [Paps of Jura, prominenceIn, Hebridean landscape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prominenceIn Context triple: [Paps of Jura, prominenceIn, Hebridean landscape]
-
A.
hasProminence
Indicates that one entity stands out in importance, visibility, or influence relative to others within a given context.
-
B.
prominence
Indicates that an entity stands out in importance, visibility, or influence relative to others within a given context.
-
C.
prominenceContext
chosen
Indicates the situational or contextual conditions under which something attains prominence or stands out relative to other things.
-
D.
prominenceStatus
Indicates the degree to which something is notable, distinguished, or stands out in importance or visibility relative to others.
-
E.
isMostProminentIn
Indicates that an entity stands out as the most notable, influential, or dominant among comparable entities within a specified context or domain.
- 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_69c687f2c9508190a60b9aad31d3f358 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad071b0081909b96dd4b93414bd1 |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:01 p.m.