Triple
T38386850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Promissory Oaths Act 1868 |
E899600
|
entity |
| Predicate | typeOfOathCovered |
P201003
|
FINISHED |
| Object | oath of allegiance |
—
|
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: oath of allegiance | Statement: [Promissory Oaths Act 1868, typeOfOathCovered, oath of allegiance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfOathCovered Context triple: [Promissory Oaths Act 1868, typeOfOathCovered, oath of allegiance]
-
A.
hasTypeOfOath
chosen
Indicates that an oath is associated with or classified by a specific type or category of oath.
-
B.
hasOathTo
Indicates a relationship in which one entity is bound by an oath or sworn commitment to another entity.
-
C.
oathAdministeredUnder
Indicates that an oath was formally given or imposed under the authority, conditions, or context of a specified person, body, or legal framework.
-
D.
oathSwornBefore
Indicates that an oath or solemn promise has been formally declared in the presence of a specified person, group, or authority.
-
E.
containsOathBy
Indicates that one entity (such as a text, document, or statement) includes or features an oath made by another entity.
- 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_69f76e5c9b808190b486523f5c2f817d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.