Triple
T3391800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Title 11 of the United States Code |
E71436
|
entity |
| Predicate | proceduralScope |
P35569
|
FINISHED |
| Object | bankruptcy procedure |
—
|
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: bankruptcy procedure | Statement: [Title 11 of the United States Code, proceduralScope, bankruptcy procedure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proceduralScope Context triple: [Title 11 of the United States Code, proceduralScope, bankruptcy procedure]
-
A.
encodingScope
Indicates the range or extent of content or information that is covered, represented, or captured by a particular encoding.
-
B.
definesScopeFor
Indicates that one entity establishes or delimits the scope, boundaries, or applicability within which another entity operates or is interpreted.
-
C.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
D.
protocolScope
chosen
Indicates that one entity defines or constrains the contextual scope within which a particular protocol, procedure, or set of interaction rules applies to another entity.
-
E.
scopeOfDeclaration
Indicates the syntactic region or context within which a particular declaration is valid and can be referenced.
- 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb850594c81909b6f8a384fc98cb2 |
completed | March 8, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69adadf705608190975423779430cc58 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:14 p.m.