Triple
T106305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 80-253 |
E2143
|
entity |
| Predicate | branchAffected |
P3304
|
FINISHED |
| Object | executive branch of the United States |
—
|
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 branch of the United States | Statement: [Public Law 80-253, branchAffected, executive branch of the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: branchAffected Context triple: [Public Law 80-253, branchAffected, executive branch of the United States]
-
A.
branchChecked
Indicates that a specific branch (such as in version control or a decision tree) has been examined or verified.
-
B.
branchType
Indicates the specific kind or category of branch that an entity belongs to or is associated with.
-
C.
branchPosition
Indicates the relative location or placement of something along a branch.
-
D.
usedByBranch
chosen
Indicates that something (such as a resource, configuration, or component) is utilized or depended upon by a particular branch.
-
E.
affectedArea
Indicates the specific region or extent over which an event, condition, or influence has an impact.
- 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_69a24e0a5b7c81908d52da08c60dabc4 |
completed | Feb. 28, 2026, 2:08 a.m. |
| NER | Named-entity recognition | batch_69a256ec650c8190bee2067e37065527 |
completed | Feb. 28, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69a2563d33788190999d471b486d5603 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:12 a.m.