Triple
T79667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Defence of the Constitutions of Government of the United States of America |
E1598
|
entity |
| Predicate | timeOfCreation |
P1936
|
FINISHED |
| Object | late 1780s |
—
|
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: late 1780s | Statement: [A Defence of the Constitutions of Government of the United States of America, timeOfCreation, late 1780s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfCreation Context triple: [A Defence of the Constitutions of Government of the United States of America, timeOfCreation, late 1780s]
-
A.
createdIn
Indicates that one entity was brought into existence, produced, or originated within the context, location, or time frame specified by another entity.
-
B.
time
chosen
Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
-
C.
inUseSince
Indicates that an entity has been actively in use starting from a specified point in time.
-
D.
createdAfterEvent
Indicates that the creation of one entity occurred after a specified event in time.
-
E.
acquisitionDate
Indicates the date on which one entity formally acquires or takes ownership 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_69a24c60d19c8190a1b6c105ca59ef5b |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a24fd16c248190a6ee4cd96c388772 |
completed | Feb. 28, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69a24eb126b48190b410b859c1be99aa |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.