Triple
T8933683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | presidential oath of office of Liberia |
E212720
|
entity |
| Predicate | canBeTakenAs |
P2819
|
FINISHED |
| Object | oath |
—
|
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 | Statement: [presidential oath of office of Liberia, canBeTakenAs, oath]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeTakenAs Context triple: [presidential oath of office of Liberia, canBeTakenAs, oath]
-
A.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
B.
canBeTakenQuickly
Indicates that the action or resource can be obtained, completed, or utilized in a short amount of time.
-
C.
canAlsoBe
chosen
Indicates that something has an additional possible state, role, or classification beyond its primary one.
-
D.
canTakeActionWith
Indicates that one entity is able or permitted to perform an action jointly or in coordination with another entity.
-
E.
canBeHeldWith
Indicates that two entities are compatible or suitable to be held or used together at the same time.
- 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_69ca8395c438819087d7cb844ab5990c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc668fa87c8190bfeda820368b89e4 |
completed | April 1, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed3286c8190a21de2ee11f2639f |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:57 p.m.