Triple
T28897816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl |
E732874
|
entity |
| Predicate | laterPublisherAssociatedWith |
P58728
|
FINISHED |
| Object | HumaNature Studios |
—
|
NE NERFINISHED |
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: HumaNature Studios | Statement: [Earl, laterPublisherAssociatedWith, HumaNature Studios]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterPublisherAssociatedWith Context triple: [Earl, laterPublisherAssociatedWith, HumaNature Studios]
-
A.
publisherAssociatedWith
Indicates a relationship where a publisher is connected or linked to another entity, such as by publishing, distributing, or otherwise being involved with its content or materials.
-
B.
laterPrimaryPublisher
chosen
Indicates that one entity served as a subsequent or later primary publisher of another entity, following an earlier primary publisher.
-
C.
formerPublisher
Indicates that one entity previously served as the publisher of another entity but no longer holds that role.
-
D.
laterEditionPublisherOfWork
Indicates that a publisher is responsible for issuing a later edition of a previously existing work.
-
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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: April 28, 2026, 8 a.m.