Triple
T22650489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Link (React Router) |
E559078
|
entity |
| Predicate | acceptsProp |
P46693
|
FINISHED |
| Object | to |
—
|
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: to | Statement: [Link (React Router), acceptsProp, to]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceptsProp Context triple: [Link (React Router), acceptsProp, to]
-
A.
usesProp
chosen
Indicates that one entity employs, utilizes, or makes use of a particular property, resource, or object in performing an action or fulfilling a function.
-
B.
supportsProp
Indicates that one entity provides assistance, endorsement, or backing for a particular property, attribute, or characteristic of another entity.
-
C.
haveProperty
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
-
D.
laterAccepts
Indicates that one entity accepts, approves, or agrees to something at a time subsequent to a referenced earlier point or event.
-
E.
hasProposed
Indicates that one entity has formally suggested or put forward something (such as an idea, plan, or offer) to another entity for consideration or acceptance.
- 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_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. |
Created at: April 17, 2026, 3:05 p.m.