Triple
T27844233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Manual of British Vertebrate Animals |
E703769
|
entity |
| Predicate | placeOfRelevance |
P162677
|
FINISHED |
| Object | Britain |
—
|
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: Britain | Statement: [A Manual of British Vertebrate Animals, placeOfRelevance, Britain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfRelevance Context triple: [A Manual of British Vertebrate Animals, placeOfRelevance, Britain]
-
A.
relatedPlace
Indicates a relationship where one place is connected or associated with another place in a relevant or meaningful way.
-
B.
relevanceIn
chosen
Indicates that something is pertinent or applicable within a specified context, scope, or domain.
-
C.
subjectLocality
Indicates that one entity serves as the geographic or jurisdictional area associated with, relevant to, or governing the other entity.
-
D.
locationGaveRiseTo
Indicates that a particular location is the origin or source from which something (such as an event, movement, phenomenon, or entity) emerged or developed.
-
E.
relevanceToCity
Indicates that something has a meaningful connection, impact, or applicability to a particular city.
- 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 27, 2026, 6:05 p.m.