Triple
T4837899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Wrekin |
E108105
|
entity |
| Predicate | hasAssociatedPhrase |
P53846
|
FINISHED |
| Object | going all around the Wrekin |
—
|
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: going all around the Wrekin | Statement: [The Wrekin, hasAssociatedPhrase, going all around the Wrekin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedPhrase Context triple: [The Wrekin, hasAssociatedPhrase, going all around the Wrekin]
-
A.
hasTerm
Indicates that an entity includes, is associated with, or is defined by a specific term or condition.
-
B.
hasNotablePhrase
chosen
Indicates that an entity is associated with a specific phrase or expression that is considered notable or characteristic of it.
-
C.
usedPhrase
Indicates that one entity employed or expressed a particular phrase in speech, writing, or another form of communication.
-
D.
associatedWithVerb
Indicates that one entity is connected or linked to another through some verb-based relationship or action.
-
E.
hasConnotation
Indicates that one entity carries an implied or associated meaning, tone, or emotional nuance in relation to another entity.
- 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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c21c7f08190846049d31fdfa144 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:25 p.m.