Triple
T22650504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Link (React Router) |
E559078
|
entity |
| Predicate | propRelative |
P149066
|
FINISHED |
| Object | relative routing behavior |
—
|
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: relative routing behavior | Statement: [Link (React Router), propRelative, relative routing behavior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propRelative Context triple: [Link (React Router), propRelative, relative routing behavior]
-
A.
isRelatively
Indicates that one entity is being described, measured, or evaluated in relation to another entity or reference point, rather than in absolute terms.
-
B.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
C.
appointedRelative
Indicates that one entity has formally assigned or designated another entity, who is a relative, to a specific role, position, or responsibility.
-
D.
isRelativeTo
Indicates that one entity has a familial or kinship relationship to another entity.
-
E.
possibleRelative
Indicates a relationship where one entity may be related to another by family or kinship, but the exact nature of the relationship is uncertain or not fully established.
- 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.