Triple
T22931988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GTR Tests database |
E569465
|
entity |
| Predicate | dataSubmission |
P63094
|
FINISHED |
| Object | voluntary by test providers |
—
|
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: voluntary by test providers | Statement: [GTR Tests database, dataSubmission, voluntary by test providers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataSubmission Context triple: [GTR Tests database, dataSubmission, voluntary by test providers]
-
A.
submissionBy
Indicates that one entity is the submitter or originator of a particular submission associated with another entity.
-
B.
submissionBasis
Indicates the basis, criteria, or grounds on which something is submitted or filed (e.g., a document, application, or claim).
-
C.
submissionSystem
chosen
Indicates a relationship where something is provided or turned in through a designated system or platform for receiving submissions.
-
D.
submittedTo
Indicates that one entity has formally sent or presented something (such as a document, request, or work) to another entity for consideration, review, or processing.
-
E.
data
Indicates that one entity serves as informational content, measurements, or recorded values associated with 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_69e2458f7d008190901dccbaebeaba24 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1813260608190bb9e1ca704c7e12f |
completed | April 29, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:44 p.m.