Triple
T15685938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Embassy Saigon |
E380199
|
entity |
| Predicate | periodOfOperation |
P802
|
FINISHED |
| Object | Vietnam War era |
—
|
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: Vietnam War era | Statement: [U.S. Embassy Saigon, periodOfOperation, Vietnam War era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodOfOperation Context triple: [U.S. Embassy Saigon, periodOfOperation, Vietnam War era]
-
A.
operatedDuring
chosen
Indicates that an action, process, or system was functioning or in operation throughout a specified time period or event.
-
B.
operatedSince
Indicates that an entity has been in operation continuously from a specified starting time or date.
-
C.
daysOfOperation
Indicates the specific days on which an entity (such as a service, facility, or operation) is active or functioning.
-
D.
operatedAt
Indicates that an operation, procedure, or activity was performed at a specific location or facility.
-
E.
initiallyOperated
Indicates that an entity first began functioning, being used, or carrying out its intended operation at a specified initial time or under initial conditions.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f4b73d881908ec0f21393a01969 |
completed | April 16, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69deda8c856c8190882330114f9a1a5f |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:44 a.m.