Triple
T10506846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fernando Henrique Cardoso |
E247808
|
entity |
| Predicate | honorificSuffix |
P341
|
FINISHED |
| Object | FHC |
E247808
|
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: FHC | Statement: [Fernando Henrique Cardoso, honorificSuffix, FHC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FHC Context triple: [Fernando Henrique Cardoso, honorificSuffix, FHC]
-
A.
FHC
chosen
FHC is the commonly used acronym and honorific referring to Fernando Henrique Cardoso, a prominent Brazilian sociologist and former president of Brazil.
-
B.
FHP
FHP is the state law enforcement agency responsible for highway safety and traffic enforcement across Florida’s roadways.
-
C.
HFC
HFC is the common abbreviation for Hibernian Football Club, a professional football team based in Edinburgh, Scotland.
-
D.
FED
FED is the commonly used abbreviation for the Fluids Engineering Division, a professional group focused on research and advancements in fluid mechanics and related technologies.
-
E.
FED
FED is the commonly used abbreviation for the Faculty of Engineering and Design, an academic unit focused on engineering and design education and research.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509b17cd88190b37e41b3ce2b4b16 |
completed | April 7, 2026, 1:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d90de6e9508190a1cdf348ec542dd5 |
completed | April 10, 2026, 2:49 p.m. |
Created at: April 6, 2026, 12:26 p.m.