Triple
T24818120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States–Vietnam relations |
E620980
|
entity |
| Predicate | beganAsModernForm |
P29102
|
FINISHED |
| Object | post–World War II 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: post–World War II era | Statement: [United States–Vietnam relations, beganAsModernForm, post–World War II era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganAsModernForm Context triple: [United States–Vietnam relations, beganAsModernForm, post–World War II era]
-
A.
emergedInModernForm
chosen
Indicates that something developed into or appeared in its current recognizable form during the modern era.
-
B.
isModernFormOf
Indicates that one entity is a newer or contemporary version, adaptation, or evolution of another earlier entity.
-
C.
modernFormSince
Indicates that an entity has existed in its current or modern form starting from a specified point in time.
-
D.
hasModernFormulationIn
Indicates that something has a contemporary or updated version expressed or formulated within a specified context, framework, or medium.
-
E.
modernEraStart
Indicates the point in time when the modern era begins for a given subject or context.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:03 a.m.