Triple
T9101970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Committee of Detail |
E218379
|
entity |
| Predicate | presentedDraftOn |
P35702
|
FINISHED |
| Object | August 6, 1787 |
—
|
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: August 6, 1787 | Statement: [Committee of Detail, presentedDraftOn, August 6, 1787]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentedDraftOn Context triple: [Committee of Detail, presentedDraftOn, August 6, 1787]
-
A.
presentedOn
Indicates that something (such as information, a work, or a performance) is shown, displayed, or delivered on a particular medium, platform, or occasion.
-
B.
documentDraftedAt
Indicates the time or place at which a document was initially drafted or created.
-
C.
presentedAtTime
chosen
Indicates that an event, action, or item was presented or occurred at a specific point in time.
-
D.
proposalDate
Indicates the date on which a proposal is formally made or submitted from one entity to another.
-
E.
hasDraft
Indicates that one entity possesses or is associated with a preliminary or unfinished version of 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_69ca83db7448819090d0a5de842ef2ac |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc971435d08190b5007ed44ac0a364 |
completed | April 1, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:15 p.m.