Triple
T3435346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portuguese Air Force |
E72438
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
FAP
FAP is the acronym for the Portuguese Air Force, the aerial warfare branch of Portugal’s Armed Forces.
|
E357569
|
NE FINISHED |
How this triple was built (4 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: FAP | Statement: [Portuguese Air Force, abbreviation, FAP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FAP Context triple: [Portuguese Air Force, abbreviation, FAP]
-
A.
FAP
FAP is the acronym for the Peruvian Air Force, the aerial warfare branch of Peru’s armed forces.
-
B.
FAS
FAS is a common abbreviation for the Faculty of Arts and Science, an academic division that typically encompasses a wide range of humanities, social science, and natural science disciplines at a university.
-
C.
FAB
FAB is the acronym for the Brazilian Air Force, the aerial warfare branch of Brazil’s armed forces.
-
D.
F.A.C.
F.A.C. is the standard legal abbreviation used to refer to the Florida Administrative Code, which contains the administrative rules and regulations of the state of Florida.
-
E.
FAPSI
FAPSI was a Russian government agency responsible for signals intelligence, secure communications, and information security, functioning as a successor to parts of the Soviet KGB.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: FAP Triple: [Portuguese Air Force, abbreviation, FAP]
Generated description
FAP is the acronym for the Portuguese Air Force, the aerial warfare branch of Portugal’s Armed Forces.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: FAP Target entity description: FAP is the acronym for the Portuguese Air Force, the aerial warfare branch of Portugal’s Armed Forces.
-
A.
FAP
FAP is the acronym for the Peruvian Air Force, the aerial warfare branch of Peru’s armed forces.
-
B.
FAS
FAS is a common abbreviation for the Faculty of Arts and Science, an academic division that typically encompasses a wide range of humanities, social science, and natural science disciplines at a university.
-
C.
FAB
FAB is the acronym for the Brazilian Air Force, the aerial warfare branch of Brazil’s armed forces.
-
D.
F.A.C.
F.A.C. is the standard legal abbreviation used to refer to the Florida Administrative Code, which contains the administrative rules and regulations of the state of Florida.
-
E.
FAPSI
FAPSI was a Russian government agency responsible for signals intelligence, secure communications, and information security, functioning as a successor to parts of the Soviet KGB.
- F. None of above. chosen
Provenance (5 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_69ad85af50288190a854b76653deee6f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9c3300881909f5c3544f8923b41 |
completed | March 8, 2026, 6:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b3547fd15481909c310b731231d5bb |
completed | March 13, 2026, 12:04 a.m. |
| NEDg | Description generation | batch_69b3588a03c08190aaed9a22837f2c0d |
completed | March 13, 2026, 12:21 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69b358e305548190b861e5ecbb59fa56 |
completed | March 13, 2026, 12:22 a.m. |
Created at: March 8, 2026, 3:16 p.m.