Triple
T12769149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beth Johanssen |
E305199
|
entity |
| Predicate | relationshipToHermesCrew |
P106807
|
FINISHED |
| Object | youngest crew member |
—
|
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: youngest crew member | Statement: [Beth Johanssen, relationshipToHermesCrew, youngest crew member]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToHermesCrew Context triple: [Beth Johanssen, relationshipToHermesCrew, youngest crew member]
-
A.
relationshipToHeistCrew
Indicates the specific role, connection, or association an entity has with a particular heist crew.
-
B.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
-
C.
relationshipWithTitans
Indicates a relationship or association that an entity has with one or more Titans, such as alliances, conflicts, or other significant interactions.
-
D.
relationshipToHannah
Indicates the specific type of relationship or connection that an entity has to Hannah.
-
E.
relationshipToCreature
Indicates a specified type of relational connection that one entity has toward a particular creature.
- F. None of above. chosen
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_69d7bdf2b43c819098ae5aa68e61ea58 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96df3b2f88190b37b696400178795 |
completed | April 10, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69d96409739881909174ba005a986cb5 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d87078c819083ea724238992204 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:28 p.m.