Triple
T27795644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act of March 1, 1872 |
E701200
|
entity |
| Predicate | locatedArea |
P107807
|
FINISHED |
| Object | Wyoming Territory |
—
|
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: Wyoming Territory | Statement: [Act of March 1, 1872, locatedArea, Wyoming Territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedArea Context triple: [Act of March 1, 1872, locatedArea, Wyoming Territory]
-
A.
所在地エリア
Indicates the geographical area or region in which an entity is located or based.
-
B.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
-
C.
locationTerritory
chosen
Indicates that one entity is geographically or administratively situated within the territorial bounds or jurisdiction of another entity.
-
D.
venueArea
Indicates the physical size or spatial extent of a venue, typically measured in units such as square meters or square feet.
-
E.
hasNearbyGeographicalArea
Indicates that one geographical area is located in close spatial proximity to another geographical area.
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ff246e0d4481908bcec718e1d4025b |
completed | May 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69ff23cb70ac81909b776ace4597ae9c |
completed | May 9, 2026, 12:08 p.m. |
Created at: April 27, 2026, 5:31 p.m.