Triple
T25114401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meriam family |
E629087
|
entity |
| Predicate | hasHistoricHouseNamedAfter |
P73450
|
FINISHED |
| Object | Meriam House |
—
|
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: Meriam House | Statement: [Meriam family, hasHistoricHouseNamedAfter, Meriam House]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricHouseNamedAfter Context triple: [Meriam family, hasHistoricHouseNamedAfter, Meriam House]
-
A.
historicallyAssociatedHouse
Indicates that there is a historical connection or association between an entity and a particular house, such as residence, ownership, or significant events tied to that location.
-
B.
houseNamedAfter
chosen
Indicates that a house or building bears a name derived from or in honor of a particular person, place, event, or entity.
-
C.
containsHistoricHouse
Indicates that one entity includes or encompasses a historic house within its boundaries or composition.
-
D.
historicallyNamedAfter
Indicates that one entity received its name from another entity at some point in the past.
-
E.
hasHeritageSiteNamedAfter
Indicates that one entity has a heritage site that is named after another entity.
- 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 18, 2026, 6:27 a.m.