Triple
T2832084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Jersey Plan |
E62261
|
entity |
| Predicate | proposedBranchStructure |
P18917
|
FINISHED |
| Object | plural executive |
—
|
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: plural executive | Statement: [New Jersey Plan, proposedBranchStructure, plural executive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedBranchStructure Context triple: [New Jersey Plan, proposedBranchStructure, plural executive]
-
A.
possibleBranch
Indicates that one entity can serve as an alternative or potential continuation path branching from another entity.
-
B.
definesBranch
chosen
Indicates that one entity specifies or establishes a particular branch or subdivision of another entity.
-
C.
parentBranch
Indicates that one branch serves as the direct ancestor or source from which another branch originates or is derived.
-
D.
viaStructure
Indicates that one entity is connected to or accessed through a particular structural element or medium.
-
E.
branchesFrom
Indicates that one entity originates or diverges from another as a subordinate or offshoot path, structure, or lineage.
- 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_69ab4c3c39188190955b9c49d98463d8 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdebe95188190bf65fb4cd88e2ec5 |
completed | March 7, 2026, 8:15 a.m. |
| PD | Predicate disambiguation | batch_69abdd0acab881909e8c25cbef83678c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:01 p.m.