Triple
T17714485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greg Norman |
E442159
|
entity |
| Predicate | designedGolfCourses |
P128695
|
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: [Greg Norman, designedGolfCourses, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedGolfCourses Context triple: [Greg Norman, designedGolfCourses, yes]
-
A.
landscapeDesignedBy
Indicates that a particular landscape or outdoor environment was planned, created, or shaped by a specific designer or design entity.
-
B.
wellDesignation
Indicates that an entity is assigned a specific well identifier or label, typically denoting its position or role within a well-based system (such as a plate or grid of wells).
-
C.
trackDesigner
Indicates that one entity is the designer or creator responsible for the layout or structure of a track associated with another entity.
-
D.
designedIn
Indicates that something was created, planned, or conceived during a particular time period or at a specific location.
-
E.
designedGame
Indicates that one entity is the creator or designer responsible for the conception and development of a particular game.
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4747f217081909010f396caaf03be |
completed | April 19, 2026, 6:21 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
| PDg | Predicate description generation | batch_69e3d018227c8190b6624a2199e765e8 |
completed | April 18, 2026, 6:40 p.m. |
Created at: April 10, 2026, 10:06 a.m.