Triple
T27014614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Ly Hayslip |
E680489
|
entity |
| Predicate | warExperienced |
P61727
|
FINISHED |
| Object | Vietnam War |
—
|
NE NERFINISHED |
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 | Statement: [Le Ly Hayslip, warExperienced, Vietnam War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warExperienced Context triple: [Le Ly Hayslip, warExperienced, Vietnam War]
-
A.
conflictExperience
chosen
Indicates that an entity has undergone or been involved in a conflict, such as a dispute, struggle, or confrontation.
-
B.
hadMilitaryServiceFrom
Indicates that an entity performed or was engaged in military service starting from a specified point in time.
-
C.
WWIIExperience
Indicates that an entity has a specific involvement, role, or personal history related to World War II.
-
D.
worldWar
Indicates a large-scale armed conflict involving multiple nations across different regions of the world, typically encompassing numerous battles, alliances, and theaters of war.
-
E.
warEndedHere
Indicates that a particular war or armed conflict came to its conclusion at this location.
- 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_69eeeb53939c8190bd431f32b060f01f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621ff76fc81908b6f456b31d43833 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 7:05 a.m.