Triple
T26987361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astonishing Tales #6 |
E679769
|
entity |
| Predicate | characterLaterKnownAs |
P144948
|
FINISHED |
| Object | Mockingbird |
—
|
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: Mockingbird | Statement: [Astonishing Tales #6, characterLaterKnownAs, Mockingbird]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterLaterKnownAs Context triple: [Astonishing Tales #6, characterLaterKnownAs, Mockingbird]
-
A.
laterBecameKnownAs
chosen
Indicates that an entity was previously known by one name or identity and, at a later time, came to be known by a different name or identity.
-
B.
isPartlyKnownAs
Indicates that an entity is known by a particular name or label in some, but not all, contexts or sources.
-
C.
alsoKnownAs
Indicates that one entity is an alternative name, alias, or designation for another entity.
-
D.
protagonistAlsoKnownAs
Indicates that an entity serving as a protagonist is alternatively referred to by another name or alias.
-
E.
formerCharacter
Indicates that an entity was once a character in a work or series but is no longer an active or current character.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 27, 2026, 6:49 a.m.