Triple
T18567242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five Yuan system |
E453786
|
entity |
| Predicate | addsBranchBeyond |
P132561
|
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: [Five Yuan system, addsBranchBeyond, executive branch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsBranchBeyond Context triple: [Five Yuan system, addsBranchBeyond, executive branch]
-
A.
extendsBetween
Indicates a relationship where one entity spans or stretches from one point, object, or boundary to another, covering the space between them.
-
B.
parentBranch
Indicates that one branch serves as the direct ancestor or source from which another branch originates or is derived.
-
C.
plannedBranch
Indicates that one entity is a planned or proposed branch (e.g., location, office, or division) associated with another entity, rather than an already existing branch.
-
D.
affectedBranch
Indicates that one entity is a branch that is impacted or influenced by the state or actions associated with another entity.
-
E.
definesBranch
Indicates that one entity specifies or establishes a particular branch or subdivision of another entity.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53aff027481909ca7257967967650 |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:43 a.m.