Triple
T37129005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puppy Co. |
E919466
|
entity |
| Predicate | relatedOrganizationInFiction |
P104242
|
FINISHED |
| Object | Baby Corp |
E1066263
|
NE 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: Baby Corp | Statement: [Puppy Co., relatedOrganizationInFiction, Baby Corp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedOrganizationInFiction Context triple: [Puppy Co., relatedOrganizationInFiction, Baby Corp]
-
A.
relatedToInFiction
Indicates that one entity is connected to another within a fictional context, such as a story, universe, or narrative work.
-
B.
worksForFictionalOrganization
Indicates that an entity is employed by or affiliated as a worker with a fictional organization.
-
C.
fictionalUniverseOrganizationLed
Indicates that an organization is led or headed by a particular entity within a fictional universe.
-
D.
associatedWithFictionalGroup
chosen
Indicates that an entity has a connection or affiliation with a fictional group, organization, or collective.
-
E.
containsFictionalOrganization
Indicates that one entity includes or features a fictional organization as part of its content or composition.
- F. None of above.
Provenance (4 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a402ba5965481909ef4d9b4e7608192 |
completed | June 27, 2026, 7:59 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.