Triple
T9198134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISSN Register |
E220766
|
entity |
| Predicate | containsDataAbout |
P86949
|
FINISHED |
| Object | title of serial |
—
|
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: title of serial | Statement: [ISSN Register, containsDataAbout, title of serial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsDataAbout Context triple: [ISSN Register, containsDataAbout, title of serial]
-
A.
typeOfInformation
Indicates that one entity specifies the category or kind of information that characterizes or describes another entity.
-
B.
dataSubject
Indicates that one entity is the individual to whom the personal data or information in question relates.
-
C.
dataHidden
Indicates that certain data is concealed, inaccessible, or not visible to users or systems under normal conditions.
-
D.
trainingDataIncludes
Indicates that one entity’s training dataset contains or incorporates the other entity as part of its data.
-
E.
collectsDataFor
Indicates that one entity gathers or records data on behalf of, or for the benefit of, another entity.
- 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_69ca83e7ba70819088b74866d9da2c30 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd87f50e88190940e73af1deda747 |
completed | April 1, 2026, 8:34 a.m. |
| PD | Predicate disambiguation | batch_69cc660af2408190ae06eb8326e1c64e |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc6745c17881908df72443e0800068 |
completed | April 1, 2026, 12:31 a.m. |
Created at: March 30, 2026, 7:25 p.m.