Triple
T27485333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mid Pines Inn and Golf Club |
E693720
|
entity |
| Predicate | hasGolfFormat |
P164326
|
FINISHED |
| Object | stroke play |
—
|
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: stroke play | Statement: [Mid Pines Inn and Golf Club, hasGolfFormat, stroke play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGolfFormat Context triple: [Mid Pines Inn and Golf Club, hasGolfFormat, stroke play]
-
A.
hasGolfDestination
Indicates that one entity serves as a golf-related destination or location for another entity.
-
B.
hasGolfInstruction
Indicates that one entity provides or is associated with golf-related teaching, coaching, or instructional services to another entity.
-
C.
hasGolfCourse
Indicates that one entity possesses, contains, or includes a golf course as part of its facilities or attributes.
-
D.
allowsHickoryGolf
Indicates that one entity permits the use or play of hickory golf by another entity.
-
E.
hasPuttingGreen
Indicates that an entity includes or provides access to a putting green as a feature or amenity.
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f644de4a84819087ddb84757fc4585 |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f643e818d481908fc66bc91bd25d77 |
completed | May 2, 2026, 6:35 p.m. |
Created at: April 27, 2026, 1:02 p.m.