Triple
T34600335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Aircraft Factory D.H.5 |
E888442
|
entity |
| Predicate | enteredFrontlineService |
P182876
|
FINISHED |
| Object | mid-1917 |
—
|
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: mid-1917 | Statement: [Royal Aircraft Factory D.H.5, enteredFrontlineService, mid-1917]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredFrontlineService Context triple: [Royal Aircraft Factory D.H.5, enteredFrontlineService, mid-1917]
-
A.
enteredService
Indicates that an entity began active use or operation at a specific time or in a specific context.
-
B.
frontlineService
Indicates that an entity provides direct, first-point-of-contact service or support to end users or customers.
-
C.
frontLineService
Indicates that an entity provides direct, first-contact service or support to customers, clients, or the public.
-
D.
enteredServiceRole
Indicates that an entity has begun serving in a particular role, position, or capacity.
-
E.
enteredServiceOn
Indicates the date or time when an entity first began active use, operation, or service.
- 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_69f349d489d48190ba30e7d97c6f5ef9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f794f24e588190965e39b77534d53f |
completed | May 3, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f791cad5e08190a8a04ca283dbecaa |
completed | May 3, 2026, 6:19 p.m. |
Created at: May 1, 2026, 2:03 a.m.