Triple
T23281011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moore Park Golf Course |
E588861
|
entity |
| Predicate | hasDrivingRangeBays |
P143299
|
FINISHED |
| Object | multi-level |
—
|
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: multi-level | Statement: [Moore Park Golf Course, hasDrivingRangeBays, multi-level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDrivingRangeBays Context triple: [Moore Park Golf Course, hasDrivingRangeBays, multi-level]
-
A.
numberOfBays
Indicates the count of distinct bays associated with or contained within a given entity.
-
B.
hasDrivingRange
Indicates that an entity (such as a vehicle or device) has a specific maximum distance it can travel or operate on a given amount of energy or fuel.
-
C.
hasChargeRange
Indicates that an entity is associated with a minimum and maximum charge value defining the range of charge it can have or support.
-
D.
chargingLocation
Indicates the place or facility where an entity is being or can be charged (e.g., electrically powered or re-energized).
-
E.
hasBays
chosen
Indicates that something possesses or contains one or more bays, such as recessed areas, compartments, or harbor inlets.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19642b46481909fd455acd2155792 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:56 p.m.