Triple
T4600486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belinda |
E100306
|
entity |
| Predicate | firstAppearanceWorkDate |
P4114
|
FINISHED |
| Object | 1697 |
—
|
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: 1697 | Statement: [Belinda, firstAppearanceWorkDate, 1697]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAppearanceWorkDate Context triple: [Belinda, firstAppearanceWorkDate, 1697]
-
A.
firstIntroductionDate
Indicates the date on which an entity was first introduced or presented for the first time.
-
B.
firstAppearedAt
Indicates the point in time or specific event at which an entity was first introduced, observed, or became known.
-
C.
firstAppeared
chosen
Indicates the earliest known time or context in which an entity was introduced, observed, or came into existence.
-
D.
firstReachedDate
Indicates the date on which a particular entity first achieved, accessed, or arrived at a specified state, location, or milestone.
-
E.
firstUsedOn
Indicates the date, time, or context in which something was initially applied, activated, or put into use on a particular object or 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_69bd43cbc014819098b45f435908f88a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5971f448819090f6e76c7d3ffc2d |
completed | March 20, 2026, 2:28 p.m. |
| PD | Predicate disambiguation | batch_69bd522c811c81909aae4feadae33174 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:11 p.m.