Triple
T33974110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hollyburn Mountain |
E871079
|
entity |
| Predicate | isWellSigned |
P177979
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hollyburn Mountain, isWellSigned, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWellSigned Context triple: [Hollyburn Mountain, isWellSigned, true]
-
A.
isSigned
Indicates that an entity has been formally endorsed or authenticated through a signature or signing action.
-
B.
isSignedAlong
Indicates that an entity has signed or endorsed something in conjunction with another specified entity.
-
C.
alsoSignedWith
Indicates that an entity signed or endorsed something together with another specified entity, as part of the same signing action or agreement.
-
D.
isSignedConcurrentWith
Indicates that two or more signing events occur during overlapping time periods, such that they are in effect or executed concurrently.
-
E.
mayBeSignedAs
Indicates that one entity can optionally be used or recognized as the signature or signed form of another entity.
- 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_69f3499da0188190ab1a4ff06fb06a2a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f7064d37388190993b2a7305a02b9f |
completed | May 3, 2026, 8:24 a.m. |
Created at: May 1, 2026, 1:50 a.m.