Triple
T9460141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief Justice of the Texas Supreme Court |
E228123
|
entity |
| Predicate | hasNumberOfCourtMembersIncludingSelf |
P2279
|
FINISHED |
| Object | 9 |
—
|
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: 9 | Statement: [Chief Justice of the Texas Supreme Court, hasNumberOfCourtMembersIncludingSelf, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfCourtMembersIncludingSelf Context triple: [Chief Justice of the Texas Supreme Court, hasNumberOfCourtMembersIncludingSelf, 9]
-
A.
hasNumberOfJurors
Indicates the relationship specifying how many jurors are associated with a given legal case, trial, or proceeding.
-
B.
hasNumberOfVotingMembers
Indicates the specific count of individuals who hold voting rights within a given group or body.
-
C.
hasCurrentNumberOfMembers
Indicates the current count of members associated with a given entity.
-
D.
numberOfJudges
chosen
Indicates the total count of judges associated with a particular case, event, or entity.
-
E.
hasVotingMembers
Indicates that certain entities are recognized as having individuals or units with the authority to vote within a group, body, or decision-making process.
- 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_69ca843b123881909b0e60028475d12d |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fcaf610819092bcd3b871665aa5 |
completed | April 1, 2026, 8:27 p.m. |
| PD | Predicate disambiguation | batch_69cca55caaa8819089c5138e014892d3 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:52 p.m.