Triple
T21856630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North American T-6 Texan |
E539644
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | SNJ |
—
|
NE NERFINISHED |
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: SNJ | Statement: [North American T-6 Texan, alsoKnownAs, SNJ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SNJ Context triple: [North American T-6 Texan, alsoKnownAs, SNJ]
-
A.
SNJ
chosen
SNJ is the U.S. Navy variant of the North American T-6 Texan advanced trainer aircraft used extensively during and after World War II.
-
B.
SNO
SNO is the National Rail station code for St Neots railway station in Cambridgeshire, England.
-
C.
SNM
SNM is the abbreviation for the Slovak National Museum, the central institution for preserving and presenting Slovakia’s cultural and historical heritage.
-
D.
SNC
SNC is the Southern Naval Command of the Indian Navy, responsible for training and operational readiness in India’s southern maritime region.
-
E.
SNC
SNC is the station code for Santa Clarita station, a passenger rail stop in Santa Clarita, California.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c47829648190bbe2d1d7033768ec |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0d636dc708190be34bb7ea526cfac |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 16, 2026, 6:56 p.m.