Triple
T26327404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statham End |
E662289
|
entity |
| Predicate | hasNamedCounterpart |
P6587
|
FINISHED |
| Object | Pavilion End |
—
|
NE NERFINISHED |
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: Pavilion End | Statement: [Statham End, hasNamedCounterpart, Pavilion End]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamedCounterpart Context triple: [Statham End, hasNamedCounterpart, Pavilion End]
-
A.
hasCounterpartName
Indicates that an entity has an alternative or corresponding name used as its counterpart in another context, system, or representation.
-
B.
hasGivenNameCounterpart
Indicates that one entity is the given-name (first-name) counterpart or variant of another entity, typically linking related personal names.
-
C.
hasCounterpart
chosen
Indicates that one entity corresponds to, matches, or serves as an equivalent or parallel version of another entity.
-
D.
hasCounterpartNameLanguage
Indicates that an entity’s counterpart (e.g., in another context or system) has a name expressed in a specified language.
-
E.
hasSmallerCounterpart
Indicates that one entity has another entity as its corresponding version that is smaller in size, scale, or magnitude.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 26, 2026, 10:31 p.m.