Triple
T11426978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Hanniger |
E270775
|
entity |
| Predicate | hasPastCharacteristic |
P37550
|
FINISHED |
| Object | troubled past |
—
|
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: troubled past | Statement: [Tom Hanniger, hasPastCharacteristic, troubled past]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPastCharacteristic Context triple: [Tom Hanniger, hasPastCharacteristic, troubled past]
-
A.
hasHistoricFeatures
Indicates that something possesses characteristics, elements, or attributes of historical significance.
-
B.
hasCharacteristic
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
-
C.
hasHad
Indicates that an entity previously experienced, possessed, or was involved in something at some point in the past.
-
D.
hasHistoryPeriod
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
-
E.
hasHistoryOf
chosen
Indicates that an entity has a documented prior occurrence or background of a specified condition, event, or state.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d806c000b88190bfaa646b2dc424b7 |
completed | April 9, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.