Triple
T28736668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blazegraph |
E730818
|
entity |
| Predicate | hasNotableDeployment |
P20057
|
FINISHED |
| Object | Wikidata Query Service (historically used Blazegraph) |
—
|
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: Wikidata Query Service (historically used Blazegraph) | Statement: [Blazegraph, hasNotableDeployment, Wikidata Query Service (historically used Blazegraph)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableDeployment Context triple: [Blazegraph, hasNotableDeployment, Wikidata Query Service (historically used Blazegraph)]
-
A.
notableDeployment
chosen
Indicates that an entity has been deployed or launched in a way that is particularly significant, prominent, or widely recognized.
-
B.
hasDeployment
Indicates that an entity is associated with or utilizes a specific deployment instance (e.g., of software, a model, or a system) in an operational context.
-
C.
hasNotableVersion
Indicates that an entity has a specific version or variant that is particularly significant, distinguished, or noteworthy compared to other versions.
-
D.
hasNotableVersionBy
Indicates that an entity has a notable or distinguished version, edition, or variant created or produced by a specific agent.
-
E.
hasScheduledReleases
Indicates that an entity has one or more releases planned to occur at specific future times.
- 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69ff519b65f081909902ba83b775ef85 |
completed | May 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69ff506fccdc8190bd93269589040aed |
completed | May 9, 2026, 3:19 p.m. |
Created at: April 28, 2026, 6:01 a.m.