Triple
T34266432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flagstaff, Arizona Territory, United States |
E879179
|
entity |
| Predicate | discoveryOfPlutoBy |
P412
|
FINISHED |
| Object | Clyde Tombaugh |
—
|
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: Clyde Tombaugh | Statement: [Flagstaff, Arizona Territory, United States, discoveryOfPlutoBy, Clyde Tombaugh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryOfPlutoBy Context triple: [Flagstaff, Arizona Territory, United States, discoveryOfPlutoBy, Clyde Tombaugh]
-
A.
discoveryOfPlutoYear
Indicates the calendar year in which the discovery of Pluto occurred.
-
B.
subjectOfDiscovery
Indicates that an entity is the topic, object, or focus that has been discovered in a discovery event or process.
-
C.
hasDiscoveryYearOfCharon
Indicates that an entity has, as its associated value, the calendar year in which Charon was discovered.
-
D.
discoveredBy
chosen
Indicates that something was found, identified, or brought to light through the efforts or actions of a particular agent.
-
E.
causeOfDiscovery
Indicates that one entity is the reason or factor that led to the discovery of another entity.
- 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_69f349b4f5fc819094b441d18e95e5f1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 1, 2026, 1:56 a.m.