Triple
T15156764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stone Court |
E362098
|
entity |
| Predicate | governmentBranchLevel |
P1085
|
FINISHED |
| Object | federal |
—
|
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: federal | Statement: [Stone Court, governmentBranchLevel, federal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentBranchLevel Context triple: [Stone Court, governmentBranchLevel, federal]
-
A.
governmentBranchAlongside
Indicates that one branch of government exists or operates alongside another as a parallel or coequal component within the same governmental system.
-
B.
governmentBranch
Indicates that one entity functions as an official division or branch within the structure of a government.
-
C.
governmentBranchEmpowered
Indicates that a particular branch of government has been granted the authority or power to perform a specified function or exercise certain responsibilities.
-
D.
governmentBranchServed
Indicates that an entity has served in or been a member of a particular branch of government.
-
E.
levelOfGovernment
chosen
Indicates the specific tier or layer within a governmental hierarchy (e.g., local, regional, national) at which an entity operates or an action is taken.
- 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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0060c62b08190bcdbd912d011d1ba |
completed | April 15, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:08 a.m.