Triple
T23560162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jackson |
E579214
|
entity |
| Predicate | hasMisadventures |
P152793
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Jackson, hasMisadventures, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMisadventures Context triple: [Jackson, hasMisadventures, yes]
-
A.
hasRomanticMisadventures
Indicates that an entity experiences a series of problematic, comical, or unsuccessful romantic relationships or encounters.
-
B.
hasSoloAdventure
Indicates that an entity participates in or is associated with an adventure undertaken alone, without companions.
-
C.
hasMystery
Indicates that one entity possesses, contains, or is associated with something unknown, secret, or unexplained in relation to another entity.
-
D.
hadMission
Indicates that an entity (such as a person, organization, or vehicle) was assigned or carried out a specific mission or operation.
-
E.
hadLesserMysteries
Indicates that an entity conducted, possessed, or was associated with the “lesser mysteries,” typically a preliminary or lower-tier set of ritualistic or esoteric practices in relation to another entity or context.
- 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_69e245fe24588190888f3aec8407d8e3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1af672db4819087dbff2c0dfadd7f |
completed | April 29, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:12 p.m.