Triple
T17693600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matteo Hessel |
E441098
|
entity |
| Predicate | hasAcademicOutput |
P34352
|
FINISHED |
| Object | conference papers |
—
|
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: conference papers | Statement: [Matteo Hessel, hasAcademicOutput, conference papers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAcademicOutput Context triple: [Matteo Hessel, hasAcademicOutput, conference papers]
-
A.
hasResearchOutput
chosen
Indicates that an entity produces, is associated with, or is responsible for a particular research output or scholarly work.
-
B.
hasNotableResearchOutput
Indicates that an entity is associated with significant, recognized, or influential research results or publications.
-
C.
scholarlyActivity
Indicates engagement in academic or research-related work, such as studying, teaching, publishing, or conducting scholarly inquiry.
-
D.
hasNotablePublicationType
Indicates that an entity is associated with a publication of a specific notable type or category.
-
E.
hasResearcher
Indicates that an entity is associated with or linked to a specific researcher responsible for work, study, or investigation related to it.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4715485d88190b9b6f347ff85d7c7 |
completed | April 19, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:04 a.m.