Triple
T20600858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L.A.M.F. Records |
E506174
|
entity |
| Predicate | namedAfterReleaseYear |
P140725
|
FINISHED |
| Object | 1977 |
—
|
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: 1977 | Statement: [L.A.M.F. Records, namedAfterReleaseYear, 1977]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterReleaseYear Context triple: [L.A.M.F. Records, namedAfterReleaseYear, 1977]
-
A.
precededByReleaseYear
Indicates that one entity’s release year occurs earlier in time than the release year of another entity.
-
B.
namedAfterAwardYear
Indicates that one entity is named after the year in which a particular award was given or received.
-
C.
namedAfterSince
Indicates that one entity has borne the name of another entity starting from a specific point in time.
-
D.
laterReleasedIn
Indicates that one entity was released at a later time or date than another entity, establishing a chronological order between their release events.
-
E.
laterReleaseYear
Indicates that the release year of one entity occurs after the release year of another entity.
- F. None of above. chosen
Provenance (4 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_69e0b4ba6ae88190af871e1f9522c704 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa1ffd088190adeacb9fe4907530 |
completed | April 20, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a9f3f88190b961db9aca36f7da |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:41 a.m.