Triple
T33070334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | An Minh |
E846216
|
entity |
| Predicate | isInDelta |
P175772
|
FINISHED |
| Object | Mekong Delta |
—
|
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: Mekong Delta | Statement: [An Minh, isInDelta, Mekong Delta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInDelta Context triple: [An Minh, isInDelta, Mekong Delta]
-
A.
hasDeltaNear
Indicates that one entity has a delta (change or difference) whose value lies within a specified proximity to another entity’s delta.
-
B.
containsDelta
Indicates that one entity includes or encompasses a change, difference, or delta associated with another entity.
-
C.
hasDelta
Indicates that there is a change, difference, or deviation between two related states, values, or versions of something.
-
D.
hasDeltaType
Indicates that one entity is associated with a specific type or category of change (delta) relative to another entity or state.
-
E.
hasDeltaLikeFeature
Indicates that one entity possesses a characteristic or attribute that is similar to or reminiscent of a delta.
- 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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: May 1, 2026, 1:25 a.m.