Triple
T6781541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GUF |
E155693
|
entity |
| Predicate | isDistinctFrom |
P1612
|
FINISHED |
| Object | FRA |
E5364
|
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: FRA | Statement: [GUF, isDistinctFrom, FRA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FRA Context triple: [GUF, isDistinctFrom, FRA]
-
A.
FRA
FRA is the standard abbreviation used to refer to the Royal Moroccan Air Force, the aerial warfare branch of Morocco’s armed forces.
-
B.
FRA
FRA is the acronym for the Global Forest Resources Assessment, a periodic FAO-led study that evaluates the state and trends of the world’s forests.
-
C.
FRA
chosen
FRA is the three-letter ISO 3166-1 alpha-3 country code that uniquely identifies France in international standards and data systems.
-
D.
FRA
FRA is the United States government agency responsible for regulating and overseeing the nation’s railroad safety, infrastructure, and operations.
-
E.
FRA
FRA is the three-letter IATA airport code for Frankfurt Airport, one of Europe’s busiest international aviation hubs located in Frankfurt, Germany.
- 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_69c688162bf8819088b664b5c3b5be7a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d26c621c8190a6eddc0d395e13e4 |
completed | March 27, 2026, 6:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c712d27a388190ab44e6e754019fca |
completed | March 27, 2026, 11:29 p.m. |
Created at: March 27, 2026, 2:14 p.m.