Triple
T31742336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution Bench |
E810174
|
entity |
| Predicate | canHaveMoreThan |
P62241
|
FINISHED |
| Object | 5 judges |
—
|
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: 5 judges | Statement: [Constitution Bench, canHaveMoreThan, 5 judges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canHaveMoreThan Context triple: [Constitution Bench, canHaveMoreThan, 5 judges]
-
A.
canBeExceededIn
Indicates that one entity’s value, level, or extent is capable of being surpassed by that of another entity within a specified context.
-
B.
hasMultiple
chosen
Indicates that an entity is associated with more than one instance or occurrence of another related entity.
-
C.
isMore
Indicates that one entity has a greater amount, degree, or value than another entity in a specified dimension or measure.
-
D.
canBeMultiple
Indicates that the related item, value, or association is allowed to occur more than once rather than being restricted to a single instance.
-
E.
cannotExceed
Indicates that one quantity, value, or limit must not be greater than another specified quantity or threshold.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ab4a67348190b431329957c70213 |
completed | May 3, 2026, 1:56 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:25 p.m.