Triple
T25043292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Les Dingodossiers |
E627167
|
entity |
| Predicate | workPeriodWithGoscinny |
P7950
|
FINISHED |
| Object | mid-1960s |
—
|
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: mid-1960s | Statement: [Les Dingodossiers, workPeriodWithGoscinny, mid-1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workPeriodWithGoscinny Context triple: [Les Dingodossiers, workPeriodWithGoscinny, mid-1960s]
-
A.
cycleWithinLaComédieHumaine
Indicates that a work belongs to a specific internal cycle or sub-series within Balzac’s larger collection *La Comédie Humaine*.
-
B.
workPeriod
chosen
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
-
C.
associatedPeriodInFiction
Indicates a relationship where a fictional work, character, or event is linked to a specific time period within its fictional universe or narrative setting.
-
D.
workedOnCharacter
Indicates that an entity contributed effort or labor to developing, portraying, or otherwise engaging with a particular character.
-
E.
partOfWorkPeriod
Indicates that a specific time span is contained within, and belongs to, a larger defined work period.
- 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_69e2ff2b4c80819087c916b2b16241b9 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4530d80148190b959bb48ff7e0c2f |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:08 a.m.