Triple
T14508468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | THINKFilm |
E340329
|
entity |
| Predicate | notableReleasePeriod |
P25964
|
FINISHED |
| Object | early 2000s |
—
|
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: early 2000s | Statement: [THINKFilm, notableReleasePeriod, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableReleasePeriod Context triple: [THINKFilm, notableReleasePeriod, early 2000s]
-
A.
notableProductionYear
Indicates the year in which an entity produced something considered notable or significant.
-
B.
notableCoverReleaseYear
Indicates the year in which a particularly notable or significant cover version of a work was released.
-
C.
notableRelease
Indicates that an entity is a significant or prominent release (such as a major version, edition, or launch) associated with another entity.
-
D.
notableWorkPeriod
chosen
Indicates the time span during which an entity produced or was associated with its most significant or well-known works.
-
E.
notableEditionYear
Indicates the year in which a particular edition of something (such as a work, product, or publication) is considered notable or significant.
- 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de94e40e44819084f323f8f9982b75 |
completed | April 14, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:21 a.m.