Triple
T396958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article V |
E9203
|
entity |
| Predicate | dateDrafted |
P9891
|
FINISHED |
| Object | 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: 1787 | Statement: [Article V, dateDrafted, 1787]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateDrafted Context triple: [Article V, dateDrafted, 1787]
-
A.
draftedIn
Indicates that one entity was selected or recruited into another entity (such as a team, organization, or military service) through a formal draft process.
-
B.
draftedUnder
Indicates that one entity was formally selected or conscripted into a role, position, or service according to the authority, rules, or jurisdiction of another entity.
-
C.
undraftedYear
Indicates the year in which an individual was eligible for a draft but was not selected by any team.
-
D.
draftedInContextOf
chosen
Indicates that something was written, prepared, or formulated specifically within the circumstances, situation, or framework of a particular context.
-
E.
signedAsUndraftedFreeAgentBy
Indicates that a player joined a team by signing a contract as an undrafted free agent, rather than being selected in a draft.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ec8a941081909a152fda0ce24a98 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96d17d08190878d3a68b17d51ca |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.