Triple
T15325176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article IV territorial district judge |
E366390
|
entity |
| Predicate | oathRequiredBy |
P82766
|
FINISHED |
| Object | federal law |
—
|
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 law | Statement: [Article IV territorial district judge, oathRequiredBy, federal law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oathRequiredBy Context triple: [Article IV territorial district judge, oathRequiredBy, federal law]
-
A.
requiredOathType
chosen
Indicates that a specific type of oath is mandated or expected in the context of a given relationship or action.
-
B.
hasOathTo
Indicates a relationship in which one entity is bound by an oath or sworn commitment to another entity.
-
C.
oathSwornBefore
Indicates that an oath or solemn promise has been formally declared in the presence of a specified person, group, or authority.
-
D.
oath
Indicates a formal, binding promise or pledge made by one party to uphold certain duties, truths, or obligations, often under conditions of solemnity or authority.
-
E.
requiredRiderOath
Indicates that an individual is obligated to take or uphold a specific rider’s oath as a condition for participation or status.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dfd8f048190831b463a2728eafe |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:16 a.m.