Triple
T2832087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Jersey Plan |
E62261
|
entity |
| Predicate | judiciaryChosenBy |
P42746
|
FINISHED |
| Object | 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: executive | Statement: [New Jersey Plan, judiciaryChosenBy, executive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: judiciaryChosenBy Context triple: [New Jersey Plan, judiciaryChosenBy, executive]
-
A.
justicesSelectedFrom
Indicates that certain justices are chosen or appointed from a particular group, body, or pool of candidates.
-
B.
hasJudiciary
Indicates that an entity possesses, is served by, or is under the authority of a judicial body or legal court system.
-
C.
chiefJusticeAppointedBy
Indicates that a particular chief justice is selected and formally given their position by a specified appointing authority.
-
D.
characterizesJudiciaryAs
Indicates that one entity portrays, describes, or evaluates the judiciary in a particular way or with specific attributes.
-
E.
judicialBody
Indicates that an entity serves as a court or tribunal with authority to adjudicate legal disputes or interpret and apply the law.
- 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_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. |
| PDg | Predicate description generation | batch_69abddccd50c8190a975942f46cfc01f |
completed | March 7, 2026, 8:11 a.m. |
Created at: March 6, 2026, 10:01 p.m.