Triple
T6964315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAW |
E161448
|
entity |
| Predicate | namesakeNotability |
P46758
|
FINISHED |
| Object | first female combat pilot in the world |
—
|
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: first female combat pilot in the world | Statement: [SAW, namesakeNotability, first female combat pilot in the world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namesakeNotability Context triple: [SAW, namesakeNotability, first female combat pilot in the world]
-
A.
hasNamesakeNotability
Indicates that one entity is notable or recognized specifically because it shares the same name as another entity.
-
B.
namesakeDescription
chosen
Indicates that the object provides a descriptive explanation of why or how the subject is considered a namesake of something or someone.
-
C.
namesakeStatus
Indicates that one entity serves as the namesake of another, or that two entities share a relationship based on having the same name.
-
D.
namesakeFullName
Indicates that one entity’s full name is used as the namesake or source of the name for another entity.
-
E.
notableNickname
Indicates that one entity is a well-known or widely recognized nickname or moniker for another 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_69c68853cff881908439d488924a8283 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6daf2b7bc8190a3e73f3b24f0352b |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c0b0a08190b262dfc94992994d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:30 p.m.