Triple
T15515049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. nationals |
E368813
|
entity |
| Predicate | shareWith |
P118953
|
FINISHED |
| Object | U.S. citizens the duty of allegiance to the United States |
—
|
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: U.S. citizens the duty of allegiance to the United States | Statement: [U.S. nationals, shareWith, U.S. citizens the duty of allegiance to the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareWith Context triple: [U.S. nationals, shareWith, U.S. citizens the duty of allegiance to the United States]
-
A.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
B.
sharesAuthorWith
Indicates that two entities have at least one author in common.
-
C.
sharesFeatureWith
Indicates that two entities have at least one common attribute, property, or characteristic in common.
-
D.
sharesModuleWith
Indicates that two entities are associated with or participate in at least one common module.
-
E.
sharesSystemWith
Indicates that two entities operate within or are associated with the same overarching system or environment.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e04031e62c8190953b61207142af15 |
completed | April 16, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57165288190979b7acb71ad5145 |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 4:02 a.m.