Triple
T13599193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Jacson |
E324898
|
entity |
| Predicate | linkedDate |
P57503
|
FINISHED |
| Object | 1940-08-21 |
—
|
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: 1940-08-21 | Statement: [Frank Jacson, linkedDate, 1940-08-21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedDate Context triple: [Frank Jacson, linkedDate, 1940-08-21]
-
A.
linkedToDate
chosen
Indicates that an entity is associated or connected to a specific date or point in time.
-
B.
linkedSupport
Indicates a relationship where one entity provides support that is directly connected or dependent on another entity’s support or status.
-
C.
linkedDocument
Indicates that one document is associated with or references another document in a meaningful way.
-
D.
linkedLocation
Indicates that one location is associated or connected to another location in a meaningful way, such as being related, referenced, or contextually tied.
-
E.
linkedDataset
Indicates that one dataset is connected or associated with another dataset, typically to show a relevant relationship or dependency between them.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb0795acc8190a08667ab9dcb0d44 |
completed | April 12, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.