Triple
T29938846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FSR |
E760439
|
entity |
| Predicate | firstReleaseBy |
P63531
|
FINISHED |
| Object | AMD |
—
|
NE NERFINISHED |
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: AMD | Statement: [FSR, firstReleaseBy, AMD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstReleaseBy Context triple: [FSR, firstReleaseBy, AMD]
-
A.
firstReleaseArtist
chosen
Indicates that the subject is the artist associated with the first release of the object (such as a work, recording, or release).
-
B.
firstRelease
Indicates that one entity is the initial or earliest release (in time or sequence) of another entity, such as a product, work, or version.
-
C.
initialReleaseFor
Indicates that one entity is the first or original release version associated with another entity (such as a work, product, or edition).
-
D.
firstAnnouncedBy
Indicates that one entity is the original source or originator that publicly disclosed, reported, or made known another entity or item for the first time.
-
E.
firstReleasedAs
Indicates the original title or form under which an entity (such as a work, product, or version) was initially released before any later re-releases, renamings, or editions.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a016336c58081909c58c5772e6fb488 |
completed | May 11, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_6a0160f25d8081909a6aaa375e9850b0 |
completed | May 11, 2026, 4:54 a.m. |
Created at: April 29, 2026, 6:21 p.m.