Triple
T24173524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur Dudley Dobson |
E599210
|
entity |
| Predicate | notablePlaceDiscovered |
P91990
|
FINISHED |
| Object | Arthur's Pass |
—
|
NE NERFINISHED |
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: Arthur's Pass | Statement: [Arthur Dudley Dobson, notablePlaceDiscovered, Arthur's Pass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlaceDiscovered Context triple: [Arthur Dudley Dobson, notablePlaceDiscovered, Arthur's Pass]
-
A.
notableDiscoveryAtSite
chosen
Indicates that an entity is recognized for having made an important discovery at a particular site.
-
B.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
C.
notablePlaceCreated
Indicates that an entity is the creator or originator of a particular notable place or location.
-
D.
discoveredByTourism
Indicates that something became known, recognized, or brought to attention as a result of tourism activity or tourist presence.
-
E.
subjectOfDiscovery
Indicates that an entity is the topic, object, or focus that has been discovered in a discovery event or process.
- 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_69e288cbd62881909de32ca64a70c17b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:33 p.m.