Triple
T15173843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bristol Type 142 |
E362554
|
entity |
| Predicate | civilRegistrationPrefix |
P7142
|
FINISHED |
| Object | G- |
—
|
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: G- | Statement: [Bristol Type 142, civilRegistrationPrefix, G-]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: civilRegistrationPrefix Context triple: [Bristol Type 142, civilRegistrationPrefix, G-]
-
A.
civilRegistrationPrefixExample
Indicates that there is an example of a standard prefix used in civil registration identifiers or records.
-
B.
civilRegistration
Indicates the official recording of a person’s vital life event (such as birth, marriage, or death) by a civil authority.
-
C.
civilRegistrationCategory
Indicates the specific type or classification of a civil registration event or record associated with an entity.
-
D.
namePrefix
Indicates that one entity is a prefix or leading part of another entity’s name.
-
E.
registrationPrefix
chosen
Indicates that an entity has a specific registration prefix code assigned to it as part of its official registration or identification.
- 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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006501b488190a2ab09dbf1532571 |
completed | April 15, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:09 a.m.