Triple
T2721513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Park Historic District (Troy) |
E60089
|
entity |
| Predicate | hasOwnershipType |
P7585
|
FINISHED |
| Object | privately owned park at its center |
—
|
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: privately owned park at its center | Statement: [Washington Park Historic District (Troy), hasOwnershipType, privately owned park at its center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOwnershipType Context triple: [Washington Park Historic District (Troy), hasOwnershipType, privately owned park at its center]
-
A.
ownershipType
chosen
Indicates the specific nature or category of the ownership relationship that one entity holds over another.
-
B.
ownsAssetType
Indicates that an entity possesses ownership rights over an asset of a specified type.
-
C.
hasEstateType
Indicates that an entity possesses or is associated with a particular category or type of estate.
-
D.
hasTypeOfOrganization
Indicates that an entity is classified as belonging to a particular type or category of organization.
-
E.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
- 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_69ab4b746d248190958e052045c09255 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdab1cb808190b0789c76bc9cb090 |
completed | March 7, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69abd82586f88190a98f60d3247fe2d3 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.