Triple
T30132975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dan Garrett |
E765896
|
entity |
| Predicate | rightsLaterAcquiredBy |
P99188
|
FINISHED |
| Object | Charlton Comics |
—
|
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: Charlton Comics | Statement: [Dan Garrett, rightsLaterAcquiredBy, Charlton Comics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rightsLaterAcquiredBy Context triple: [Dan Garrett, rightsLaterAcquiredBy, Charlton Comics]
-
A.
acquiredRightsTo
Indicates that one entity has obtained legal or contractual ownership, control, or usage rights over something previously held by another entity.
-
B.
laterRightsHolderOfWork
chosen
Indicates that the subject is a subsequent rights holder who acquired the rights to the work after an earlier rights holder.
-
C.
rightsManagement
Indicates the management, control, and enforcement of usage rights or permissions associated with an entity or resource.
-
D.
rightsRecognizedIn
Indicates that certain rights are formally acknowledged or upheld within a specified context, such as a legal system, jurisdiction, or document.
-
E.
rightHolder
Indicates that one entity holds or possesses a legal or contractual right in relation to another entity or resource.
- 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_69f22477d1a081908df2b7e6ed16859d |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67e4a4b5c8190b5bc97169f9153de |
completed | May 2, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:15 p.m.