Triple
T12580476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank family |
E300321
|
entity |
| Predicate | hidingStartYear |
P105543
|
FINISHED |
| Object | 1942 |
—
|
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: 1942 | Statement: [Frank family, hidingStartYear, 1942]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hidingStartYear Context triple: [Frank family, hidingStartYear, 1942]
-
A.
cleanupStartYear
Indicates the year in which a cleanup process or remediation effort begins.
-
B.
dateHidden
Indicates that the date associated with an item, event, or record is intentionally concealed or not displayed.
-
C.
optionalYearBefore
Indicates that one entity may, but does not necessarily, occur or be valid in a year that precedes the year associated with another entity.
-
D.
settingStartYear
Indicates the year in which a particular setting, configuration, or condition first becomes effective or begins to apply.
-
E.
beganInYear
Indicates that an event, process, or state started in a specific calendar year.
- F. None of above. chosen
Provenance (4 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
| PDg | Predicate description generation | batch_69d954e351f88190869220d46e0ce282 |
completed | April 10, 2026, 7:52 p.m. |
Created at: April 9, 2026, 5:01 p.m.