Triple
T36481913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon Territory Organic Act |
E898837
|
entity |
| Predicate | locationOfDocument |
P158312
|
FINISHED |
| Object | United States Statutes at Large |
E625
|
NE FINISHED |
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 Statutes at Large | Statement: [Oregon Territory Organic Act, locationOfDocument, United States Statutes at Large]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfDocument Context triple: [Oregon Territory Organic Act, locationOfDocument, United States Statutes at Large]
-
A.
locationInDocument
Indicates that one entity specifies where another entity is situated or referenced within a document.
-
B.
documentLocation
chosen
Indicates the physical or digital place where a document is stored, kept, or can be accessed.
-
C.
documentationLocation
Indicates the place or resource where relevant documentation for an entity can be found.
-
D.
locationOfPassage
Indicates the place or area through which a passage, route, or transit occurs or is situated.
-
E.
objectLocation
Indicates that one entity is located at, in, or on another entity or spatial region.
- F. None of above.
Provenance (4 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39cfdcfd2881908ddd007bb6f94a80 |
completed | June 23, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.