Triple
T8495324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Man in the Maze |
E201083
|
entity |
| Predicate | hasTimePeriodOfWriting |
P75539
|
FINISHED |
| Object | late 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: late 1960s | Statement: [The Man in the Maze, hasTimePeriodOfWriting, late 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimePeriodOfWriting Context triple: [The Man in the Maze, hasTimePeriodOfWriting, late 1960s]
-
A.
hasDateWritten
Indicates that something is associated with the specific date on which it was written.
-
B.
hasWrittenFor
Indicates that one entity has created written content (such as articles, stories, or texts) for or on behalf of another entity, typically a publication, organization, or platform.
-
C.
periodWrittenIn
chosen
Indicates the time period during which something was written or created.
-
D.
writtenDuring
Indicates that the creation or authorship of something took place within a specified time period or historical event.
-
E.
hasWrittenAbout
Indicates that one entity has authored content or material discussing, analyzing, or referencing another 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe57dbe488190af5f06faf862cd5d |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:13 p.m.