Triple
T18534772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Straus Park |
E452933
|
entity |
| Predicate | memorialSubjectRelationship |
P63144
|
FINISHED |
| Object | married couple |
—
|
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: married couple | Statement: [Straus Park, memorialSubjectRelationship, married couple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memorialSubjectRelationship Context triple: [Straus Park, memorialSubjectRelationship, married couple]
-
A.
relatedMemorial
Indicates a relationship where one entity serves as a memorial or commemorative reference to another entity.
-
B.
commemorativeRelation
Indicates a relationship where one entity serves to honor, remember, or memorialize another entity, event, or person.
-
C.
memorialRole
Indicates that an entity holds a specific role, capacity, or function in relation to a memorial or commemorative context.
-
D.
historicalRelationship
Indicates a relationship that existed between entities in the past, often tied to a specific historical period, context, or event.
-
E.
isCommemorationSubject
chosen
Indicates that an entity serves as the focus or object of a commemorative act, event, or artifact.
- 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53400d548819080b17f30b3ee7174 |
completed | April 19, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:37 a.m.