Triple
T21581437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venetia Burney |
E532532
|
entity |
| Predicate | proposedNameYear |
P35031
|
FINISHED |
| Object | 1930 |
—
|
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: 1930 | Statement: [Venetia Burney, proposedNameYear, 1930]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedNameYear Context triple: [Venetia Burney, proposedNameYear, 1930]
-
A.
proposedInYear
Indicates that something, such as a plan, idea, or piece of legislation, was formally put forward or suggested in a specific calendar year.
-
B.
usedNameToYear
Indicates that a particular name was in use or valid during a specified year.
-
C.
namedAfterReleaseYear
Indicates that something is given a name derived from or corresponding to the year it was released.
-
D.
nameProposedBy
chosen
Indicates that one entity is the proposer or originator of a particular name assigned to another entity.
-
E.
nameProposedIn
Indicates that a particular name was suggested or put forward within a specific proposal, context, or 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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeeb5c496c819093113dd5790fca48 |
completed | April 27, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:31 p.m.