Triple
T25545311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linda Rogo |
E640282
|
entity |
| Predicate | hasComplexPast |
P184571
|
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: [Linda Rogo, hasComplexPast, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComplexPast Context triple: [Linda Rogo, hasComplexPast, true]
-
A.
hasComplex
Indicates that one entity possesses, is associated with, or is part of a larger composite structure or complex formed with another entity.
-
B.
hasPriorHistory
Indicates that an entity has a previously recorded occurrence, condition, or involvement relevant to the current context.
-
C.
usedInPast
Indicates that an entity has been utilized or employed at some point in the past, prior to the current time or context.
-
D.
usedInPastFor
Indicates that one entity was previously utilized for another entity or purpose in the past.
-
E.
usedInPastBy
Indicates that an entity was previously utilized or employed by another entity at some time in the past.
- 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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f7b365288c8190bcb11fcfba028737 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2f2b9ac8190aa05b8a1aa18ec2d |
completed | May 3, 2026, 8:41 p.m. |
Created at: April 21, 2026, 3:28 p.m.