Triple
T3080125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berwickshire |
E64234
|
entity |
| Predicate | hasChapmanCode |
P45746
|
FINISHED |
| Object | BEW |
—
|
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: BEW | Statement: [Berwickshire, hasChapmanCode, BEW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChapmanCode Context triple: [Berwickshire, hasChapmanCode, BEW]
-
A.
hasProgramCode
Indicates that an entity is associated with a specific program identifier or code used to reference or classify it within a system.
-
B.
hasChorusBy
Indicates that something (typically a musical work or song) includes a chorus section that is performed, written, or provided by a specified entity.
-
C.
hasChorus
Indicates that something (typically a song or musical piece) includes a chorus section as part of its structure.
-
D.
hasCP
Indicates that an entity possesses, is associated with, or is characterized by a specific CP (such as a control point, contact person, or configuration parameter), depending on the domain context.
-
E.
hasChant
Indicates that an entity is associated with or characterized by a particular chant.
- 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_69ad857bb4c88190a4cf27893fcabed8 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada1a9d61081909953eb2f4ad4537e |
completed | March 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69ad9debb6308190be28378ae1fc98af |
completed | March 8, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69ada0f6fef48190b13898be383a246b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:03 p.m.