Triple
T7805850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laurel Hill Golf Club |
E180546
|
entity |
| Predicate | targetPlayerLevel |
P56693
|
FINISHED |
| Object | amateur competitors |
—
|
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: amateur competitors | Statement: [Laurel Hill Golf Club, targetPlayerLevel, amateur competitors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetPlayerLevel Context triple: [Laurel Hill Golf Club, targetPlayerLevel, amateur competitors]
-
A.
teamLevel
Indicates the hierarchical rank or tier at which a team operates within an organization, competition, or structure.
-
B.
typicalEquipmentLevel
Indicates the usual or standard amount or quality of equipment associated with an entity or situation.
-
C.
playedAtLevel
Indicates that an entity participated or performed in an activity, event, or game at a specified level of difficulty, competition, or hierarchy.
-
D.
trainingLevel
Indicates the degree or stage of training or skill development that an entity has attained.
-
E.
requiresSkillLevel
chosen
Indicates that performing or engaging in something depends on possessing at least a specified level of skill.
- 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_69ca827e50cc8190a92a733577184938 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae91687788190af9cb7aaa996d291 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:35 p.m.