Triple
T34439795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SQ22 |
E884064
|
entity |
| Predicate | usesULRVariant |
P178943
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [SQ22, usesULRVariant, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesULRVariant Context triple: [SQ22, usesULRVariant, yes]
-
A.
extendedVariantUsedFor
Indicates that one entity is an extended or modified variant that is used in place of, or for the purposes of, another entity.
-
B.
usedInVariant
Indicates that something (such as a component, feature, or element) is utilized or included within a particular variant or version of a larger entity.
-
C.
usesURI
Indicates that one entity employs or references another entity via a specific Uniform Resource Identifier (URI) as its means of identification or access.
-
D.
exportVariantOf
Indicates that one entity is an exported version or externally released form derived from another, original entity.
-
E.
rulesVariantOf
Indicates that one set of rules is a modified or alternative version derived from another set of rules.
- 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f719458378819081725f544efb1173 |
completed | May 3, 2026, 9:45 a.m. |
Created at: May 1, 2026, 2 a.m.