Triple
T32850403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alberto García |
E840231
|
entity |
| Predicate | hasPublicationOn |
P80
|
FINISHED |
| Object | regular black hole solutions |
—
|
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: regular black hole solutions | Statement: [Alberto García, hasPublicationOn, regular black hole solutions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicationOn Context triple: [Alberto García, hasPublicationOn, regular black hole solutions]
-
A.
hasPublication
chosen
Indicates that an entity is associated with or responsible for a specific publication.
-
B.
hasPublishedOn
Indicates that an entity (such as an author or publisher) has released or made content publicly available on a particular platform, medium, or date.
-
C.
publishedIn
Indicates that a work (such as an article, paper, or book) has been formally released or made available within a specific venue, medium, or publication.
-
D.
hasPublicationMedium
Indicates the medium or channel through which a work or publication is disseminated or made available.
-
E.
hasPublisher
Indicates that an entity is published or issued by a specific publisher.
- 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: May 1, 2026, 1:17 a.m.