Triple
T2225286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manzanar National Historic Site |
E48634
|
entity |
| Predicate | inOperationUntil |
P2110
|
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: [Manzanar National Historic Site, inOperationUntil, 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inOperationUntil Context triple: [Manzanar National Historic Site, inOperationUntil, 1945]
-
A.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
B.
inForceUntil
chosen
Indicates that a condition, rule, or agreement remains valid and operative up to a specified time or event.
-
C.
operation
Indicates that one entity performs, carries out, or controls the functioning of another entity or system.
-
D.
subsequentOperationName
Indicates that one operation occurs later in sequence and is identified by the given subsequent operation name.
-
E.
usedInOperation
Indicates that something (such as a tool, method, or resource) is employed or applied during the execution of a particular operation or procedure.
- 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_69a88aa51b388190949868ec9766e587 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc03ffcbc8190a27e32af831c7be5 |
completed | March 7, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69abbdac31d8819092d17815e11921e9 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.