Triple
T18944250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soldiers and Sailors Park |
E463466
|
entity |
| Predicate | isPublicProperty |
P30373
|
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: [Soldiers and Sailors Park, isPublicProperty, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPublicProperty Context triple: [Soldiers and Sailors Park, isPublicProperty, true]
-
A.
isOnPrivateProperty
Indicates that the subject is located within the boundaries of property that is privately owned and not open for unrestricted public access.
-
B.
isPrivateOrPublic
Indicates whether something is designated as private or public in terms of its accessibility or visibility.
-
C.
hasPublic
Indicates that an entity is accessible or visible to the general public rather than being private or restricted.
-
D.
isPubliclyAccessible
chosen
Indicates that the referenced entity can be accessed or used by the general public without special permissions or restrictions.
-
E.
haveProperty
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
- 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d53e6e0c81908a547e21c4819bac |
completed | April 20, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 11:59 a.m.