Triple
T23485557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1967 Constitution of South Vietnam |
E570523
|
entity |
| Predicate | branchCreated |
P25959
|
FINISHED |
| Object | executive branch |
—
|
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: executive branch | Statement: [1967 Constitution of South Vietnam, branchCreated, executive branch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: branchCreated Context triple: [1967 Constitution of South Vietnam, branchCreated, executive branch]
-
A.
branchAllocation
Indicates how resources, responsibilities, or items are distributed or assigned across different branches or subdivisions.
-
B.
branchOrigin
Indicates that one entity is the source or starting point from which another entity branches or diverges.
-
C.
branchLine
Indicates a relationship where one line, route, or path diverges from and is subordinate to a main or primary line.
-
D.
developedBranch
chosen
Indicates that one branch or offshoot was created, expanded, or evolved from another as its source or origin.
-
E.
branchNumber
Indicates the specific branch identifier or code assigned to distinguish one branch from others within the same organization or system.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7538a8c8190b7effcc39a3f9787 |
completed | April 29, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:03 p.m.