Triple
T16766580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fugitive Pieces |
E407478
|
entity |
| Predicate | hasChildVersionOfCharacter |
P95841
|
FINISHED |
| Object | Young Jakob Beer |
—
|
LITERAL 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: Young Jakob Beer | Statement: [Fugitive Pieces, hasChildVersionOfCharacter, Young Jakob Beer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChildVersionOfCharacter Context triple: [Fugitive Pieces, hasChildVersionOfCharacter, Young Jakob Beer]
-
A.
hasParentCharacter
Indicates that one character is the parent of another character.
-
B.
hasChildVersionOfSinger
Indicates that one entity is a child version or younger incarnation of a singer represented by another entity.
-
C.
hasChildCharacters
chosen
Indicates that one entity includes or is associated with other entities that are considered its child characters in a hierarchical or narrative structure.
-
D.
childOfCharacter
Indicates that one character is the offspring (biological, adopted, or otherwise recognized child) of another character.
-
E.
hasSiblingCharacters
Indicates that two characters share at least one common parent, making them siblings in the narrative or data context.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b0330d6081908ce99f14c70b90f2 |
completed | April 18, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.