Triple
T31031248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verve |
E790728
|
entity |
| Predicate | firstIssuePlaceOfPublication |
P13815
|
FINISHED |
| Object | Paris |
E568
|
NE 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: Paris | Statement: [Verve, firstIssuePlaceOfPublication, Paris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstIssuePlaceOfPublication Context triple: [Verve, firstIssuePlaceOfPublication, Paris]
-
A.
placeOfFirstPublication
chosen
Indicates the location where a work was first published or made publicly available.
-
B.
firstPublicationIn
Indicates the initial venue, medium, or context in which a work was first published.
-
C.
firstPublisher
Indicates that an entity is the original or earliest publisher of another entity (such as a work, edition, or resource).
-
D.
firstIssuedAtLocation
Indicates the location where something (such as a document, license, or credential) was originally issued for the first time.
-
E.
firstCompleteEditionPlace
Indicates the place where the first complete edition of a work was published or produced.
- F. None of above.
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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a036054129081909e66c5d62015e6c1 |
completed | May 12, 2026, 5:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a292af72f508190b11b5d4d193983c4 |
completed | June 10, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_6a035f17cbf88190acd6bdbfc9789ffb |
completed | May 12, 2026, 5:10 p.m. |
Created at: April 29, 2026, 8:59 p.m.