Triple
T2263614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supermarine S.6 |
E50092
|
entity |
| Predicate | registrationContext |
P37540
|
FINISHED |
| Object | built in small numbers |
—
|
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: built in small numbers | Statement: [Supermarine S.6, registrationContext, built in small numbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registrationContext Context triple: [Supermarine S.6, registrationContext, built in small numbers]
-
A.
registrationEffect
Indicates the outcome or consequence that results from an entity being registered or from the act of registration taking place.
-
B.
registrationMode
Indicates the method or process by which something is registered or enrolled.
-
C.
registrationSystem
Indicates a system or process responsible for recording, managing, and maintaining registrations or enrollments for entities.
-
D.
relatedRegister
Indicates a relationship where one entity is associated with, linked to, or corresponds to a particular register or record in a system.
-
E.
registrationCategory
Indicates the classification or type under which an entity is formally registered within a system or registry.
- 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_69a88b01e0048190ba96431b5f990ba9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc2ea65288190bc8644a07a11dfa9 |
completed | March 7, 2026, 6:17 a.m. |
| PD | Predicate disambiguation | batch_69abbdb592588190ac1ef5e8c54575b1 |
completed | March 7, 2026, 5:55 a.m. |
| PDg | Predicate description generation | batch_69abc2e97eb0819084acb26cfa4e3946 |
completed | March 7, 2026, 6:17 a.m. |
Created at: March 4, 2026, 7:48 p.m.