Triple
T26753660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edgerton |
E674609
|
entity |
| Predicate | hasGeographicUse |
P150084
|
FINISHED |
| Object | United States |
—
|
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: United States | Statement: [Edgerton, hasGeographicUse, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeographicUse Context triple: [Edgerton, hasGeographicUse, United States]
-
A.
hasGeographicBasis
Indicates that something is grounded in, derived from, or defined by a particular geographic location or area.
-
B.
geographicalUsage
chosen
Indicates that something is used, applied, or occurs within a particular geographic area or region.
-
C.
hasGeographicType
Indicates that an entity is associated with or classified by a specific type or category of geographic feature or area.
-
D.
hasGeodeticPurpose
Indicates that something is associated with or serves a specific geodetic purpose, such as measurement, reference, or positioning in geodesy.
-
E.
hasGeographyCharacteristic
Indicates that an entity possesses a specific geographical feature, property, or attribute.
- 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_69eecda6e9dc81908452fab3ba17ed9b |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 3:54 a.m.