Triple
T28593022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hebrew Wikipedia |
E723705
|
entity |
| Predicate | projectNamespaceName |
P165467
|
FINISHED |
| Object | ויקיפדיה |
—
|
NE NERFINISHED |
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: ויקיפדיה | Statement: [Hebrew Wikipedia, projectNamespaceName, ויקיפדיה]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectNamespaceName Context triple: [Hebrew Wikipedia, projectNamespaceName, ויקיפדיה]
-
A.
providerNamespaceExample
Indicates that an example or sample is associated with a specific provider’s namespace within a system or service.
-
B.
baseNamespace
Indicates the foundational namespace from which other namespaces, identifiers, or resources are defined or derived.
-
C.
vendorNamespace
Indicates that something belongs to, is defined within, or is associated with a particular vendor’s designated namespace.
-
D.
namedSpace
Indicates that an entity has been assigned or is associated with a specific name within a particular namespace or naming context.
-
E.
previousNamespace
Indicates that one namespace directly precedes or was used before another namespace, typically in a versioning or migration context.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f659355a208190be2609ffc7a9c427 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 28, 2026, 4:21 a.m.