Triple
T34356221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William B. Finneran |
E881734
|
entity |
| Predicate | hasPavilionNamedAfterHim |
P49744
|
FINISHED |
| Object | Finneran Pavilion |
—
|
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: Finneran Pavilion | Statement: [William B. Finneran, hasPavilionNamedAfterHim, Finneran Pavilion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPavilionNamedAfterHim Context triple: [William B. Finneran, hasPavilionNamedAfterHim, Finneran Pavilion]
-
A.
hasBuildingNamedAfterHim
chosen
Indicates that a person has a building that is named in their honor.
-
B.
hasPavilion
Indicates that one entity possesses, includes, or is associated with a pavilion as part of its structure, property, or facilities.
-
C.
hasFestivalInHisHonor
Indicates that a person is honored by a festival that is held or celebrated for them.
-
D.
hasHeritageSiteNamedAfter
Indicates that one entity has a heritage site that is named after another entity.
-
E.
hasPartInHisHonor
Indicates that something includes or contains a part, section, or component that is dedicated or named in honor of a particular person.
- 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_69f349bd06008190904c2f86c42749e3 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff7dcedab08190a719a707d03306e2 |
completed | May 9, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69ff7d0119348190ad462554e81190fe |
completed | May 9, 2026, 6:29 p.m. |
Created at: May 1, 2026, 1:58 a.m.