Triple
T293195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PISA |
E6037
|
entity |
| Predicate | dataAvailability |
P7415
|
FINISHED |
| Object | publicly accessible microdata |
—
|
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: publicly accessible microdata | Statement: [PISA, dataAvailability, publicly accessible microdata]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataAvailability Context triple: [PISA, dataAvailability, publicly accessible microdata]
-
A.
dataReturned
Indicates that some data has been sent back or provided as a result of a request, query, or operation.
-
B.
dataUse
Indicates how data is intended to be accessed, processed, or applied within a particular context or activity.
-
C.
availableAs
Indicates that one entity can be used, accessed, or offered in the form, role, or capacity of another entity.
-
D.
hasLongTermDatasetSince
Indicates that an entity has maintained or used a particular dataset continuously starting from a specified point in time.
-
E.
availability
chosen
Indicates that an entity is present, accessible, or ready for use or interaction by another entity.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea0dd1dc8190aecd5afdeb2fd74b |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e934b4408190b53a17f57a02df65 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.