Triple
T339472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Commission on Terrorist Attacks Upon the United States |
E6800
|
entity |
| Predicate | heldPublicHearings |
P11604
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [National Commission on Terrorist Attacks Upon the United States, heldPublicHearings, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldPublicHearings Context triple: [National Commission on Terrorist Attacks Upon the United States, heldPublicHearings, true]
-
A.
paroleHearings
Indicates that one or more formal hearings are held to evaluate an incarcerated individual's eligibility or suitability for parole.
-
B.
convenedOn
Indicates that an event, meeting, or formal gathering took place or was held on a specific date or time.
-
C.
spokeAt
Indicates that a person delivered a talk, speech, or presentation at a particular event or location.
-
D.
hasConference
Indicates that an entity organizes, hosts, or is associated with a specific conference.
-
E.
hasDebate
Indicates that there is a formal discussion or argument between entities, typically presenting opposing viewpoints on a topic.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eae3a27c81909fc7deb600125fb1 |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e95067e88190a914a1c1d0283dfc |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea09a5e881908b313cb37409a4f9 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.