Triple
T27217401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TNI |
E681176
|
entity |
| Predicate | previousIssuerName |
P171420
|
FINISHED |
| Object | Trinity Mirror |
—
|
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: Trinity Mirror | Statement: [TNI, previousIssuerName, Trinity Mirror]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousIssuerName Context triple: [TNI, previousIssuerName, Trinity Mirror]
-
A.
issuerCurrentName
Indicates the current official name by which the issuer is presently identified.
-
B.
issuerFormerParent
Indicates that the subject entity was formerly the parent (e.g., controlling or owning entity) of the issuer entity, but no longer holds that parent status.
-
C.
issuerAlsoKnownAs
Indicates that an issuer entity is known by an alternative name, alias, or identifier.
-
D.
issuerPreviouslyInstanceOf
Indicates that the current issuer was, at some earlier time, an instance or member of the specified class, type, or category.
-
E.
issuerRenamedFrom
chosen
Indicates that an issuer currently known by one name was previously known by a different name.
- 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_69eefac9f64c8190a07490fe0c8b72a3 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 27, 2026, 9:41 a.m.