Triple
T8527195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A.V. Roe and Company |
E201846
|
entity |
| Predicate | commonName |
P570
|
FINISHED |
| Object | Avro |
E113414
|
NE 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: Avro | Statement: [A.V. Roe and Company, commonName, Avro]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Avro Context triple: [A.V. Roe and Company, commonName, Avro]
-
A.
Avro
Avro is a row-oriented, schema-based data serialization format commonly used in big data processing and storage systems.
-
B.
Avro
chosen
Avro was a British aircraft manufacturer best known for producing iconic military aircraft such as the Avro Lancaster bomber during the 20th century.
-
C.
Avro Avian
The Avro Avian was a British light biplane of the 1920s and 1930s, widely used for long-distance and record-breaking flights.
-
D.
Hawker
Hawker is a surname of English origin borne by various notable individuals across fields such as aviation, politics, and the arts.
-
E.
Avro Athena
The Avro Athena was a British postwar advanced trainer aircraft developed by Avro for the Royal Air Force.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca83228b24819085d22e7dc99f5d94 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6477100819081fa20cb6b8ea3d7 |
completed | March 31, 2026, 3:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce6d49c1408190b7c23739409d1e3d |
completed | April 2, 2026, 1:21 p.m. |
Created at: March 30, 2026, 6:16 p.m.