Triple
T32191794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Janet Tyler |
E822274
|
entity |
| Predicate | ultimatelyRelocatedWith |
P173297
|
FINISHED |
| Object | others who look like her |
—
|
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: others who look like her | Statement: [Janet Tyler, ultimatelyRelocatedWith, others who look like her]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ultimatelyRelocatedWith Context triple: [Janet Tyler, ultimatelyRelocatedWith, others who look like her]
-
A.
relocatedAfter
Indicates that one entity moved or was transferred to a new location after another specified event or relocation occurred.
-
B.
relocatedTo
Indicates that an entity has moved or been transferred from its previous location to a new specified location.
-
C.
relocatedUsing
Indicates that an entity was moved or transferred from one place to another by means of a specified method, tool, or transportation mode.
-
D.
relocatedFrom
Indicates that an entity has moved or been transferred away from a specified original location.
-
E.
relocatedDuring
Indicates that an entity changed its location or place of residence within the time span of a specified event or period.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bace6c508190a7b25ad1024151b6 |
completed | May 3, 2026, 3:02 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b42902a081909126c7322858a2b3 |
completed | May 3, 2026, 2:34 a.m. |
Created at: May 1, 2026, 12:35 a.m.