Triple
T7637035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louisburg Square |
E172903
|
entity |
| Predicate | parkOwnership |
P23570
|
FINISHED |
| Object | privately owned |
—
|
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 | Statement: [Louisburg Square, parkOwnership, privately owned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parkOwnership Context triple: [Louisburg Square, parkOwnership, privately owned]
-
A.
hasParkOwner
chosen
Indicates that an entity serves as the owner or legal controller of a particular park.
-
B.
parkAuthority
Indicates that an entity has official responsibility for managing, regulating, or overseeing a park or protected recreational area.
-
C.
hasParkingLotOwner
Indicates that a parking lot is owned or possessed by a specific owner.
-
D.
parkSystem
Indicates a relationship where an entity is part of, managed by, or associated with an organized system of parks or protected recreational areas.
-
E.
ownsPropertyIn
Indicates that one entity possesses legal ownership rights over property located within a specified place or jurisdiction.
- 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_69c69952849881908fdcea7a93bfc307 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fac953e08190a2f50bf783c49faf |
completed | March 27, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e8cadc8190b7977fcd213954dd |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:57 p.m.