Triple
T9037277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Record Plant, New York City |
E216527
|
entity |
| Predicate | famePeak |
P85819
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Record Plant, New York City, famePeak, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famePeak Context triple: [Record Plant, New York City, famePeak, 1970s]
-
A.
fameStatus
Indicates the level or state of public recognition or renown associated with an entity.
-
B.
fameFor
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
C.
claimToFame
Indicates the notable achievement, characteristic, or association for which an entity is best known.
-
D.
gainedProminenceFor
Indicates that an entity became widely recognized or notable specifically because of another entity, action, or achievement.
-
E.
mostFamousBearer
Indicates that one entity is the most widely recognized or renowned individual associated with a particular name, title, or attribute compared to all other bearers of it.
- 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_69ca83d10b608190b2b2f8e0a7faaf14 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6ac1f08c8190be0e37115df11f31 |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f6dec4081909379bd57c02a5710 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:08 p.m.