Triple
T26515225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam Meiks |
E669794
|
entity |
| Predicate | hasTroubledPast |
P16448
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Adam Meiks, hasTroubledPast, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTroubledPast Context triple: [Adam Meiks, hasTroubledPast, true]
-
A.
hasTragicPast
chosen
Indicates that an entity has experienced a significantly sorrowful or traumatic history that influences its present state or characterization.
-
B.
hasLawEnforcementHistory
Indicates that an entity has a record of past involvement with law enforcement, such as prior incidents, investigations, or offenses.
-
C.
hasHistoryOf
Indicates that an entity has a documented prior occurrence or background of a specified condition, event, or state.
-
D.
hasBackIssues
Indicates that an entity experiences or possesses problems, conditions, or complications related to its back.
-
E.
hasNegativeHistoricalAssociation
Indicates that one entity is historically linked to another in a way that is viewed as harmful, problematic, or disreputable.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 27, 2026, 1:23 a.m.