Triple
T34689934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridey Murphy |
E890862
|
entity |
| Predicate | memoriesRecordedBy |
P141703
|
FINISHED |
| Object | Morey Bernstein |
—
|
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: Morey Bernstein | Statement: [Bridey Murphy, memoriesRecordedBy, Morey Bernstein]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memoriesRecordedBy Context triple: [Bridey Murphy, memoriesRecordedBy, Morey Bernstein]
-
A.
retainsMemoriesOf
Indicates that one entity continues to hold or preserve memories about another entity or about events involving that entity.
-
B.
areRecordedBy
Indicates that an event, observation, or piece of information is captured or documented by a specific recording agent, device, or process.
-
C.
rememberedThrough
Indicates that one entity is remembered, commemorated, or kept in memory by means of, or through the influence of, another entity or medium.
-
D.
hasMemorableMoments
Indicates that something contains or is associated with particularly notable or unforgettable moments or events.
-
E.
wasRecordedBy
chosen
Indicates that an event, observation, or piece of data was captured or documented by a specific agent, instrument, or recording process.
- 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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: May 1, 2026, 2:05 a.m.