Triple
T22758874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guararapes International Airport |
E562928
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | REC |
—
|
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: REC | Statement: [Guararapes International Airport, IATAcode, REC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: REC Context triple: [Guararapes International Airport, IATAcode, REC]
-
A.
REC
REC is the standard abbreviation used by the World Wide Web Consortium (W3C) to denote a finalized, stable web standard known as a W3C Recommendation.
-
B.
REC
REC is the common abbreviation for the 1st Foreign Cavalry Regiment, an elite armored unit of the French Foreign Legion.
-
C.
REC
REC is the stock ticker symbol for Recticel Group, a Belgian company specializing in polyurethane-based insulation and engineered foam solutions.
-
D.
REC
chosen
REC is the IATA airport code for Recife/Guararapes–Gilberto Freyre International Airport, the main airport serving Recife in northeastern Brazil.
-
E.
The Rec
The Rec is a well-known sports and recreation ground, most famously serving as the home stadium of the Bath Rugby Club in Bath, England.
- 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_69e24552e11c81909c2d61578a558bd7 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17a7a8ca481909953dcd6fbcc5fcf |
completed | April 29, 2026, 3:26 a.m. |
Created at: April 17, 2026, 3:25 p.m.