Triple
T14547693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persistent Uniform Resource Locator |
E341330
|
entity |
| Predicate | redirectsTo |
P2066
|
FINISHED |
| Object | current location of a resource |
—
|
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: current location of a resource | Statement: [Persistent Uniform Resource Locator, redirectsTo, current location of a resource]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redirectsTo Context triple: [Persistent Uniform Resource Locator, redirectsTo, current location of a resource]
-
A.
directedTo
Indicates that something is sent, aimed, or addressed toward a particular target or recipient.
-
B.
returnsTo
Indicates that an entity goes back to a previous location, state, or entity it was associated with before.
-
C.
losesTo
Indicates that one entity is defeated by or comes out worse than another in a competitive or comparative context.
-
D.
followsTo
Indicates that one entity moves or proceeds behind another entity toward a specific destination or target.
-
E.
isDestinationFor
chosen
Indicates that one entity serves as the endpoint or target location that another entity is intended to reach or be directed toward.
- 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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb2ebdf9481909f4d2da1ad31099c |
completed | April 14, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69de5c546c7081909e27d504ec360c5c |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:23 a.m.