Triple
T31820161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Sons of the United States |
E812236
|
entity |
| Predicate | hasFormalDuties |
P193365
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [First Sons of the United States, hasFormalDuties, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormalDuties Context triple: [First Sons of the United States, hasFormalDuties, no]
-
A.
hasDutiesUnder
Indicates that one party is obligated to perform specific responsibilities or fulfill obligations as defined by another party, agreement, or authority.
-
B.
hasDutiesDefinedBy
Indicates that one entity’s responsibilities or obligations are specified, governed, or determined by another entity.
-
C.
hasFormalStatus
Indicates that an entity possesses an officially recognized or legally defined status within a formal system or context.
-
D.
hasPrimaryDuty
Indicates that one entity holds the main or most important responsibility or obligation toward another entity or within a specified context.
-
E.
hasDutyStatus
Indicates that an entity currently holds a particular duty or operational status in relation to a role, task, or assignment.
- F. None of above. chosen
Provenance (4 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_69f348e97fa48190aa06286962af6dee |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69fd4445f8c08190bb2dc27e0971c55d |
completed | May 8, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:45 p.m.