Triple
T23989277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Search/Retrieve Web Service |
E605018
|
entity |
| Predicate | hasQueryLanguageFullName |
P154527
|
FINISHED |
| Object | Contextual Query Language |
—
|
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: Contextual Query Language | Statement: [Search/Retrieve Web Service, hasQueryLanguageFullName, Contextual Query Language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQueryLanguageFullName Context triple: [Search/Retrieve Web Service, hasQueryLanguageFullName, Contextual Query Language]
-
A.
hasFullNameLanguage
Indicates that the language in which a full name is expressed is associated with that full name.
-
B.
isNamedLanguage
Indicates that a language entity bears a specific name or designation.
-
C.
hasSchemaLanguage
Indicates that an entity uses, conforms to, or is defined in a particular schema language.
-
D.
hasLanguageType
Indicates that an entity is associated with a particular type or category of language (e.g., spoken, written, programming, sign).
-
E.
hasFullNameUsage
Indicates that an entity uses a particular full name in a specific context or manner.
- 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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d38a40588190887c2abc6565bbf4 |
completed | April 29, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69f1615994c48190a5de95d3f7e5cd0a |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 9:37 p.m.