Triple
T28784665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ron Anderson |
E726767
|
entity |
| Predicate | hasProfessionalMisadventuresIn |
P199016
|
FINISHED |
| Object | The Tall Guy |
—
|
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: The Tall Guy | Statement: [Ron Anderson, hasProfessionalMisadventuresIn, The Tall Guy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProfessionalMisadventuresIn Context triple: [Ron Anderson, hasProfessionalMisadventuresIn, The Tall Guy]
-
A.
hasMisadventures
Indicates that an entity experiences or is involved in a series of troublesome, chaotic, or comically unfortunate events.
-
B.
hasPerilousAdventure
Indicates that an entity experiences, undertakes, or is involved in a dangerous or high-risk adventure.
-
C.
hasFictionalAccident
Indicates that an entity experiences or is involved in an accident that occurs within a fictional or imagined context.
-
D.
hasRomanticMisadventures
Indicates that an entity experiences a series of problematic, comical, or unsuccessful romantic relationships or encounters.
-
E.
hasTragicPast
Indicates that an entity has experienced a significantly sorrowful or traumatic history that influences its present state or characterization.
- 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_69f0319aabec81908368720196f69a35 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69ff1ba8694481909ceb36f26ca85612 |
completed | May 9, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69ff1b27f0f08190a9e74308c5b3d1ba |
completed | May 9, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69ff1ba7494481908678a7a0f93dbd03 |
completed | May 9, 2026, 11:33 a.m. |
Created at: April 28, 2026, 6:21 a.m.