Triple
T10753798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quaker Cemetery, Brooklyn, New York, United States |
E253636
|
entity |
| Predicate | isPrivateProperty |
P8275
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Quaker Cemetery, Brooklyn, New York, United States, isPrivateProperty, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrivateProperty Context triple: [Quaker Cemetery, Brooklyn, New York, United States, isPrivateProperty, true]
-
A.
isPrivateOrPublic
Indicates whether something is designated as private or public in terms of its accessibility or visibility.
-
B.
isPrivateCompany
Indicates that an entity operates as a privately held company, not publicly traded on a stock exchange.
-
C.
hasProprietaryStatus
Indicates that something is owned, controlled, or protected as proprietary rather than being public or freely available.
-
D.
publicOrPrivate
chosen
Indicates whether something is designated as publicly accessible or restricted to private use or access.
-
E.
isPrivatelyLeased
Indicates that an entity is under a lease agreement held by a private (non-governmental) party rather than being publicly owned or leased.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d71dc2543c8190bb060aa7a1fed6a6 |
completed | April 9, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69d6f311529c819080ca5493d55d6050 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:15 p.m.