Triple
T30134924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belmont Report |
E765961
|
entity |
| Predicate | commissionEstablishmentYear |
P165653
|
FINISHED |
| Object | 1974 |
—
|
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: 1974 | Statement: [Belmont Report, commissionEstablishmentYear, 1974]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commissionEstablishmentYear Context triple: [Belmont Report, commissionEstablishmentYear, 1974]
-
A.
hasYearOfEstablishment
chosen
Indicates the specific year in which an entity was founded, created, or formally established.
-
B.
developmentCorporationEstablishedYear
Indicates the year in which a development corporation was formally established.
-
C.
officeEstablishedWith
Indicates that an office or formal workplace was created or set up through the involvement, authorization, or collaboration of the associated entity or entities.
-
D.
coFoundedInYear
Indicates that two or more entities jointly founded something (such as an organization or company) in a specified year.
-
E.
organizationTypeFounded
Indicates the type or category of organization that was established or created in a founding event.
- 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_69f22477d1a081908df2b7e6ed16859d |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 7:16 p.m.