Triple
T22650505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Link (React Router) |
E559078
|
entity |
| Predicate | propReloadDocument |
P149067
|
FINISHED |
| Object | forces full document reload |
—
|
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: forces full document reload | Statement: [Link (React Router), propReloadDocument, forces full document reload]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propReloadDocument Context triple: [Link (React Router), propReloadDocument, forces full document reload]
-
A.
replacedDocument
Indicates that one document has been superseded or substituted by another document.
-
B.
revivedByDocument
Indicates that something previously inactive, invalid, or obsolete is brought back into effect or recognized again as a result of the contents or issuance of a specific document.
-
C.
coreDocumentOf
Indicates that one entity serves as the primary or central document associated with, or defining, another entity.
-
D.
publicDocument
Indicates that a document is officially available to the general public without access restrictions.
-
E.
affectsDocument
Indicates that one entity produces an influence or change on a document, altering its state, content, or properties.
- 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1703b40b88190aec5cf2fa28bfcbf |
completed | April 29, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:05 p.m.