Triple
T25066783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Day Fossil Beds National Monument |
E627802
|
entity |
| Predicate | USNPSParkCode |
P21993
|
FINISHED |
| Object | JODA |
—
|
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: JODA | Statement: [John Day Fossil Beds National Monument, USNPSParkCode, JODA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USNPSParkCode Context triple: [John Day Fossil Beds National Monument, USNPSParkCode, JODA]
-
A.
hasNationalParkServiceUnitCode
chosen
Indicates that an entity is associated with a specific National Park Service unit, identified by its official unit code.
-
B.
geologicalSurveyCode
Indicates that an entity is associated with a specific identifier or code used in a geological survey to reference or catalog it.
-
C.
isInNP
Indicates that one entity is located within, or is a member of, a specified noun phrase (NP) in a syntactic or semantic structure.
-
D.
UNSNumber
Indicates that an entity is associated with a specific United Nations (UN) number used to identify hazardous substances or dangerous goods.
-
E.
FIPSCode
Indicates the standardized Federal Information Processing Standards (FIPS) code assigned to identify a specific geographic or administrative 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f4599e14688190aa19833f62ffb283 |
completed | May 1, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:10 a.m.