Triple
T34368318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Foundling |
E882080
|
entity |
| Predicate | associatedWithPublicationFormat |
P5128
|
FINISHED |
| Object | book |
—
|
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: book | Statement: [A Foundling, associatedWithPublicationFormat, book]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithPublicationFormat Context triple: [A Foundling, associatedWithPublicationFormat, book]
-
A.
associatedWithPub
Indicates that an entity has a connection or relationship with a particular publication (e.g., as source, reference, or related work).
-
B.
hasPublishingFormat
chosen
Indicates that an entity is associated with a specific format or medium in which it is published or made publicly available.
-
C.
relatedFormat
Indicates that two resources are available in different but closely related formats or media representations of essentially the same content.
-
D.
associatedWithFormat
Indicates a relationship where something is linked or connected to a particular format or formatting standard.
-
E.
intendedPublicationForm
Indicates the planned or expected format in which a work is to be published (e.g., print, digital, audio).
- 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_69f349be5c9c81908dc726ae1f4c68f2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:58 a.m.