Triple
T26248704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cristina Moreno |
E656520
|
entity |
| Predicate | livesWithInWork |
P66936
|
FINISHED |
| Object | Flor Moreno |
—
|
NE NERFINISHED |
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: Flor Moreno | Statement: [Cristina Moreno, livesWithInWork, Flor Moreno]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livesWithInWork Context triple: [Cristina Moreno, livesWithInWork, Flor Moreno]
-
A.
residesInWork
Indicates that a person or entity lives or is based within the location, setting, or environment defined by a particular work (such as a book, film, or other creative piece).
-
B.
residenceInWork
chosen
Indicates that an entity’s place of residence is located within or at the same site as their place of work.
-
C.
ownsWork
Indicates that one entity has legal ownership or proprietary rights over a particular work or creation.
-
D.
placeInWork
Indicates that one entity is located or occurs within the spatial or structural context of another entity in a work.
-
E.
associatedWithWorkplace
Indicates a relationship where an entity has a connection or affiliation with a particular workplace or place of employment.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60dc8882c8190853698e6b1903853 |
completed | May 2, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 9:06 p.m.