Triple
T23496505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirkstone rock |
E571717
|
entity |
| Predicate | hasNotableShape |
P82774
|
FINISHED |
| Object | church-like profile |
—
|
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: church-like profile | Statement: [Kirkstone rock, hasNotableShape, church-like profile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableShape Context triple: [Kirkstone rock, hasNotableShape, church-like profile]
-
A.
hasDistinctiveShape
chosen
Indicates that an entity possesses a shape or form that is notably different from others and can be easily recognized or distinguished.
-
B.
hasNotableStructureOn
Indicates that a subject entity possesses or features a significant or noteworthy structure located on it.
-
C.
hasApparentShape
Indicates that one entity is perceived or observed to have a particular shape or form, regardless of its true or physical structure.
-
D.
hasHemShape
Indicates that an item possesses a specific form or contour of its hem or lower edge.
-
E.
hasIrregularShape
Indicates that an entity possesses a form or outline that deviates from a regular, standard, or symmetrical shape.
- 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_69e245b4829881909b77a70e942bbd54 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7e00384819092729319a378d4ab |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:05 p.m.