Triple
T23988955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GND |
E605010
|
entity |
| Predicate | linkedDataAvailability |
P33161
|
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: [GND, linkedDataAvailability, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedDataAvailability Context triple: [GND, linkedDataAvailability, yes]
-
A.
supportsLinkedData
chosen
Indicates that one entity provides or enables functionality for using, publishing, or interacting with Linked Data associated with another entity.
-
B.
microdataAvailability
Indicates that detailed, record-level data (microdata) associated with an entity is available for access or use.
-
C.
canBeLinkedTo
Indicates that one entity has the potential or capability to be connected or associated with another entity.
-
D.
linkedDataset
Indicates that one dataset is connected or associated with another dataset, typically to show a relevant relationship or dependency between them.
-
E.
linkedIndicator
Indicates that one indicator is associated with, derived from, or otherwise connected to another indicator.
- 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_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. |
Created at: April 17, 2026, 9:37 p.m.