Triple
T25925337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoa Hao |
E653285
|
entity |
| Predicate | strongFollowingIn |
P159841
|
FINISHED |
| Object | Mekong Delta peasants |
—
|
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: Mekong Delta peasants | Statement: [Hoa Hao, strongFollowingIn, Mekong Delta peasants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strongFollowingIn Context triple: [Hoa Hao, strongFollowingIn, Mekong Delta peasants]
-
A.
strongFollowingIn
chosen
Indicates that one entity has a large, loyal, or highly engaged group of followers or supporters in relation to another entity.
-
B.
followedIn
Indicates that one entity began following or subscribing to another entity, typically in a social or sequential context.
-
C.
followerOf
Indicates that one entity subscribes to, tracks, or regularly receives updates from another entity, typically in a social or informational context.
-
D.
followedSign
Indicates that an entity proceeded in accordance with, or took action based on, a particular sign or posted instruction.
-
E.
calledToFollowBy
Indicates that one entity has been summoned, invited, or designated by another entity to follow, accompany, or pursue a path or role associated with that other entity.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6041346c88190aa3d2c42b6e5ac5f |
completed | May 2, 2026, 2:02 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 22, 2026, 8:35 a.m.