Triple
T35760698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DANS |
E1033559
|
entity |
| Predicate | offersGuidanceOn |
P96535
|
FINISHED |
| Object | data management plans |
—
|
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: data management plans | Statement: [DANS, offersGuidanceOn, data management plans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersGuidanceOn Context triple: [DANS, offersGuidanceOn, data management plans]
-
A.
providesGuidanceTo
Indicates that one entity offers direction, advice, or instruction to another entity.
-
B.
providesAdviceOn
chosen
Indicates that one entity gives guidance, recommendations, or expert counsel to another entity regarding a particular subject or matter.
-
C.
guidanceType
Indicates the specific kind or category of guidance being provided or referenced in the relationship between entities.
-
D.
offersInformationOn
Indicates that one entity provides or makes available information about another entity or topic.
-
E.
guidanceIntegration
Indicates how one entity incorporates, applies, or aligns with the advice, instructions, or direction provided 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:06 p.m.