Triple
T9379585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golf Champion Trophy |
E225746
|
entity |
| Predicate | hasReplicaPolicy |
P88615
|
FINISHED |
| Object | original retained by The R&A |
—
|
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: original retained by The R&A | Statement: [Golf Champion Trophy, hasReplicaPolicy, original retained by The R&A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReplicaPolicy Context triple: [Golf Champion Trophy, hasReplicaPolicy, original retained by The R&A]
-
A.
hasReferencePolicy
Indicates that an entity is governed by or associated with a specific reference policy that defines how it should be used, accessed, or managed.
-
B.
hasUpdatePolicy
Indicates that one entity defines or is associated with the rules or strategy governing how another entity is updated or maintained over time.
-
C.
hasReplicaDisplays
Indicates that an entity features or presents one or more replica items as displays.
-
D.
supportsDataReplicationFactor
Indicates that an entity enables, configures, or is compatible with a specified data replication factor for storing or duplicating data.
-
E.
hasKeyPolicy
Indicates that an entity is associated with a specific key management or access control policy governing how its keys may be used or managed.
- 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_69ca842d8ee88190aaaa639aa953185d |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50bb49bc8190bdad23e120755ac7 |
completed | April 1, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:44 p.m.