Triple
T33613752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G-VLCN |
E861058
|
entity |
| Predicate | registrationOf |
P176960
|
FINISHED |
| Object | Avro Vulcan XH558 |
—
|
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: Avro Vulcan XH558 | Statement: [G-VLCN, registrationOf, Avro Vulcan XH558]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registrationOf Context triple: [G-VLCN, registrationOf, Avro Vulcan XH558]
-
A.
registrationFor
Indicates a relationship where one entity is enrolled, signed up, or formally recorded to participate in, use, or be associated with another entity (such as an event, service, or program).
-
B.
register
Indicates that an entity formally records or enrolls another entity or itself in an official system, list, or record.
-
C.
registrationExample
Indicates that an instance serves as an illustrative or sample case of a particular registration.
-
D.
inscriptionBy
Indicates that an inscription was created, written, or carved by a particular agent or entity.
-
E.
officialRegisterOf
Indicates that one entity serves as the authoritative, formally maintained record or registry for another entity.
- 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f70b0ca081908b24a98937e6ef66 |
completed | May 3, 2026, 7:19 a.m. |
Created at: May 1, 2026, 1:41 a.m.