Triple
T23283358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RSAF roundel |
E588924
|
entity |
| Predicate | appliedOnLocation |
P50393
|
FINISHED |
| Object | aircraft fuselage |
—
|
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: aircraft fuselage | Statement: [RSAF roundel, appliedOnLocation, aircraft fuselage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedOnLocation Context triple: [RSAF roundel, appliedOnLocation, aircraft fuselage]
-
A.
appliedToLocationOnVehicle
chosen
Indicates that something (such as a treatment, device, or action) is applied specifically to a particular location or area on a vehicle.
-
B.
appliedFrom
Indicates that an application or request was initiated starting at or originating from a particular source, location, or context.
-
C.
appliesAt
Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
-
D.
appliedAs
Indicates that one entity submitted itself or was put forward for consideration in a particular role, position, or context relative to another entity.
-
E.
appliedBy
Indicates that an action, process, or treatment is carried out or executed by a particular agent or entity.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196447a748190bd797ec9baa63fc3 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:58 p.m.