Triple
T14107703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chu Lai, South Vietnam |
E339547
|
entity |
| Predicate | handOverPeriod |
P112837
|
FINISHED |
| Object | early 1970s |
—
|
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: early 1970s | Statement: [Chu Lai, South Vietnam, handOverPeriod, early 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handOverPeriod Context triple: [Chu Lai, South Vietnam, handOverPeriod, early 1970s]
-
A.
handsOverTo
Indicates that one entity transfers possession, control, or responsibility of something directly to another entity.
-
B.
handedOverOfficeDuring
Indicates that one entity transferred official control, authority, or responsibility of an office or position to another entity during a specified time period.
-
C.
heldOver
Indicates that something has been continued, carried forward, or extended in effect or duration beyond its original or expected time.
-
D.
banPeriodEnd
Indicates the point in time when a ban or prohibition on an entity or action is scheduled to end.
-
E.
dateHandedOver
Indicates the specific date on which something (such as an item, document, or responsibility) was formally transferred from one party to another.
- 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de600ada808190b92d67dc30f13d15 |
completed | April 14, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:22 p.m.