Triple
T19757461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermann Park Golf Course |
E474537
|
entity |
| Predicate | hasElectricCarts |
P137209
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hermann Park Golf Course, hasElectricCarts, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectricCarts Context triple: [Hermann Park Golf Course, hasElectricCarts, yes]
-
A.
hasElectricMotor
Indicates that an entity is equipped with, contains, or uses an electric motor as part of its operation or structure.
-
B.
isElectrically
Indicates that one entity has an electrical property, connection, or interaction in relation to another entity.
-
C.
electrificationCompatibility
Indicates whether one entity can be effectively and safely powered, charged, or operated using the electrical system, standards, or infrastructure associated with another entity.
-
D.
hasElectricCharge
Indicates that an entity possesses a nonzero electric charge as a physical property.
-
E.
notableElectricVariant
Indicates that one entity is a notable or significant electric-powered version or variant of another entity.
- F. None of above. chosen
Provenance (4 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6531c42408190b856341a6c6a4101 |
completed | April 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:48 p.m.