Triple
T7111418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Form R |
E165714
|
entity |
| Predicate | dataPubliclyAvailable |
P74611
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Form R, dataPubliclyAvailable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataPubliclyAvailable Context triple: [Form R, dataPubliclyAvailable, true]
-
A.
dataPublication
Indicates that some data has been made publicly available or formally released, typically through a defined dissemination or publishing process.
-
B.
dataPortal
Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
-
C.
includesPublicCompanies
Indicates that the referenced set, group, or collection contains one or more publicly traded companies as members.
-
D.
dataSubject
Indicates that one entity is the individual to whom the personal data or information in question relates.
-
E.
dataSubjects
Indicates a relationship where certain individuals or entities are the subjects about whom data is collected, processed, or referenced.
- 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_69c6888120f081908f8f01b201dc4a4c |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5ecd4488190bf19e42de55da98b |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c4f9788190830288d00cc37026 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e456e89481908df42a1b4232a4a0 |
completed | March 27, 2026, 8:11 p.m. |
Created at: March 27, 2026, 2:43 p.m.