Triple
T16459428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whitemarsh Hall |
E399766
|
entity |
| Predicate | hasParkOrGroundsArea |
P30832
|
FINISHED |
| Object | approximately 300 acres |
—
|
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: approximately 300 acres | Statement: [Whitemarsh Hall, hasParkOrGroundsArea, approximately 300 acres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParkOrGroundsArea Context triple: [Whitemarsh Hall, hasParkOrGroundsArea, approximately 300 acres]
-
A.
hasParkArea
chosen
Indicates that an entity includes or is associated with a designated park or recreational area within its boundaries.
-
B.
hasGrassSeatingArea
Indicates that an entity includes or provides a seating area located on a grass surface.
-
C.
hasParkAndGardenGrade
Indicates that an entity has been assigned a specific quality or rating level for its parks and gardens.
-
D.
hasTennisCourt
Indicates that one entity possesses, includes, or provides access to a tennis court as part of its facilities or attributes.
-
E.
hasStandingArea
Indicates that an entity includes or provides a designated area where people can stand.
- 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32d7ff0e881909100bb5b33c04291 |
completed | April 18, 2026, 7:06 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.