Triple
T5615921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Preston Trail Golf Club |
E147476
|
entity |
| Predicate | isWellKnownIn |
P4733
|
FINISHED |
| Object | professional golf community |
—
|
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: professional golf community | Statement: [Preston Trail Golf Club, isWellKnownIn, professional golf community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWellKnownIn Context triple: [Preston Trail Golf Club, isWellKnownIn, professional golf community]
-
A.
recognizedIn
chosen
Indicates that an entity is formally acknowledged, honored, or given recognition within a particular context, setting, or domain.
-
B.
reconocidaPor
Indicates that an entity is recognized, acknowledged, or honored by another entity.
-
C.
knownFrom
Indicates that one entity is aware of, has learned about, or recognizes another entity through a specified source, context, or medium.
-
D.
haveInternationalRecognition
Indicates that an entity is formally acknowledged or accepted by the international community or by official bodies across multiple countries.
-
E.
namedIn
Indicates that one entity is explicitly mentioned or referenced by name within another entity (such as a document, statement, or record).
- 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_69c00905d4588190bd967842bbcf2219 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c021da7f848190bb1cd0270ad6398f |
completed | March 22, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69c01b1b3c98819080687d18ab10a914 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:39 p.m.