Triple
T25808336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LP record |
E650032
|
entity |
| Predicate | resurgenceReason |
P149195
|
FINISHED |
| Object | collectability |
—
|
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: collectability | Statement: [LP record, resurgenceReason, collectability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resurgenceReason Context triple: [LP record, resurgenceReason, collectability]
-
A.
restorationReason
Indicates the reason or justification for which something that was previously removed, disabled, or altered has been restored to its former state.
-
B.
revivalPurpose
Indicates that an action or event is carried out with the aim of bringing something back into use, existence, or prominence.
-
C.
reasonForCreation
Indicates that one entity was created for the purpose, cause, or motivation specified by another entity.
-
D.
reasonForReintroduction
chosen
Indicates the justification or cause that led to something being brought back or reintroduced.
-
E.
hasResurgenceNear
Indicates that an entity experiences a renewed increase, revival, or comeback in close spatial or contextual proximity to another specified entity or location.
- 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f600c2a7748190809b59109e476169 |
completed | May 2, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 7:06 a.m.