Triple
T8252829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humphrey’s Executor v. United States |
E192996
|
entity |
| Predicate | concernsOfficial |
P47677
|
FINISHED |
| Object | FTC commissioner |
—
|
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: FTC commissioner | Statement: [Humphrey’s Executor v. United States, concernsOfficial, FTC commissioner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concernsOfficial Context triple: [Humphrey’s Executor v. United States, concernsOfficial, FTC commissioner]
-
A.
strategicConcernFor
Indicates a relationship where one entity considers another entity’s situation, actions, or outcomes important for its own long-term goals, risks, or strategic interests.
-
B.
concernsRight
Indicates that something is about or relates specifically to a legal or moral right held by an entity.
-
C.
commandConcerning
Indicates that one entity issues an order or directive specifically about another entity or subject.
-
D.
formalConcern
chosen
Indicates that one entity has an official or formally recognized interest, responsibility, or involvement regarding another entity or matter.
-
E.
concern
Indicates that one entity is about, relates to, or is of interest or importance to 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_69ca82dfad9c8190b8cd18fb89f50f40 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78cbc7cc81909931440e95d6e691 |
completed | March 31, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69cb36b6d5548190b665a6cce14c69f7 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.