Triple
T9485751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tilo |
E228755
|
entity |
| Predicate | hasPersonalHistory |
P37550
|
FINISHED |
| Object | complex personal history |
—
|
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: complex personal history | Statement: [Tilo, hasPersonalHistory, complex personal history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPersonalHistory Context triple: [Tilo, hasPersonalHistory, complex personal history]
-
A.
hasHistoryOf
chosen
Indicates that an entity has a documented prior occurrence or background of a specified condition, event, or state.
-
B.
hasResearchHistory
Indicates that an entity has a documented record of past research activities, projects, or studies.
-
C.
hasHistoryNote
Indicates that there is an associated historical note or record describing past events, changes, or context related to the subject.
-
D.
hasTragicPast
Indicates that an entity has experienced a significantly sorrowful or traumatic history that influences its present state or characterization.
-
E.
hasHistoricalSection
Indicates that something includes a dedicated part or segment that presents historical information or context.
- 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_69ca84730a5081908de282651019bf2f |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd804fb2b4819084c7f5a842dbe5a6 |
completed | April 1, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69cca561e6b0819090aa795f3c3a2083 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:55 p.m.