Triple
T27615315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CodePlex |
E700424
|
entity |
| Predicate | originalWebsiteURL |
P30251
|
FINISHED |
| Object | https://www.codeplex.com |
—
|
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: https://www.codeplex.com | Statement: [CodePlex, originalWebsiteURL, https://www.codeplex.com]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalWebsiteURL Context triple: [CodePlex, originalWebsiteURL, https://www.codeplex.com]
-
A.
originalWebsite
chosen
Indicates that one entity is the original or primary website from which another entity (such as a copy, mirror, or derivative site) is derived.
-
B.
originSite
Indicates the place or site from which something or someone originally comes or is derived.
-
C.
originalSiteUse
Indicates the historical or initial functional use or purpose assigned to a particular site before any subsequent changes or developments.
-
D.
registrationOrigin
Indicates the source or context from which a registration event was initiated or created.
-
E.
formerUrl
Indicates that one entity was previously identified or accessible via the URL represented by the other entity, but that URL is no longer current.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
Created at: April 27, 2026, 2:12 p.m.