Triple
T7918901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FGB Zarya |
E183893
|
entity |
| Predicate | spacecraftType |
P4019
|
FINISHED |
| Object | FGB-1 |
E696970
|
NE 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: FGB-1 | Statement: [FGB Zarya, spacecraftType, FGB-1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FGB-1 Context triple: [FGB Zarya, spacecraftType, FGB-1]
-
A.
FGB
chosen
FGB, better known as Zarya, is the first module of the International Space Station, providing initial power and propulsion functions.
-
B.
FFG-7
FFG-7 is the hull classification symbol for USS Oliver Hazard Perry, the lead ship of the Oliver Hazard Perry-class guided-missile frigates of the United States Navy.
-
C.
CGB-001
CGB-001 is the original hardware model designation for Nintendo’s Game Boy Color handheld gaming console.
-
D.
F-2
F-2 is a three-quarter-ton model in Ford’s first-generation postwar F-Series pickup truck lineup, positioned between the lighter F-1 and heavier F-3 trucks.
-
E.
FGZ
FGZ is the FAA location identifier assigned to Sabre Army Heliport, a U.S. Army helicopter facility.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca828efbe48190bd48482650182e79 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a8fbbb48190b50def4941761a31 |
completed | March 31, 2026, 3:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc63a8b7cc8190b18a43b7d610fd55 |
completed | April 1, 2026, 12:15 a.m. |
Created at: March 30, 2026, 5:05 p.m.