Triple
T32511249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I've Got a Tiger By the Tail |
E830935
|
entity |
| Predicate | releaseDateApproximate |
P49730
|
FINISHED |
| Object | late 1964 |
—
|
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 1964 | Statement: [I've Got a Tiger By the Tail, releaseDateApproximate, late 1964]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releaseDateApproximate Context triple: [I've Got a Tiger By the Tail, releaseDateApproximate, late 1964]
-
A.
releaseApproximateYear
chosen
Indicates that an entity was released or made available around a specified year, where the year is approximate rather than exact.
-
B.
openingDateApproximate
Indicates that the date when something was opened or began is not known exactly and is only an approximate value.
-
C.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
D.
releasedAt
Indicates the time or date at which something (such as a product, work, or item) is made publicly available or officially launched.
-
E.
stableReleaseApproxDate
Indicates an approximate calendar date when a stable release of something is (or was) expected to become available.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 1, 2026, 1 a.m.