Triple
T28920873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minidoka National Historic Site |
E733507
|
entity |
| Predicate | closedAsCamp |
P177136
|
FINISHED |
| Object | 1945 |
—
|
LITERAL 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: 1945 | Statement: [Minidoka National Historic Site, closedAsCamp, 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedAsCamp Context triple: [Minidoka National Historic Site, closedAsCamp, 1945]
-
A.
closedAs
Indicates that one entity has been brought to an end, resolved, or made no longer active as a result of another entity or action.
-
B.
closedIn
Indicates that one entity is enclosed, contained, or surrounded within the boundaries or limits defined by another entity.
-
C.
closedAsMine
Indicates that an issue or report was closed because it was determined to be a duplicate of one already owned or previously handled by the closer.
-
D.
closedUnder
Indicates that applying a specified operation to elements within a set always produces a result that is also an element of that same set.
-
E.
closedBy
Indicates that one entity performs the action of closing, finishing, or terminating another entity (such as a task, issue, or process).
- F. None of above. chosen
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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f854486c81909396d944a55e03ab |
completed | May 3, 2026, 7:25 a.m. |
Created at: April 28, 2026, 8:19 a.m.