Triple
T9828952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIUC |
E238731
|
entity |
| Predicate | acronym |
P43
|
FINISHED |
| Object | IFCU |
E238730
|
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: IFCU | Statement: [FIUC, acronym, IFCU]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IFCU Context triple: [FIUC, acronym, IFCU]
-
A.
IFCU
chosen
IFCU is the acronym for the International Federation of Catholic Universities, a global association that brings together Catholic higher education institutions for collaboration in teaching, research, and service.
-
B.
IFC
IFC (Industry Foundation Classes) is an open, vendor-neutral data model standard used to enable interoperability and information exchange in Building Information Modeling (BIM) across different software platforms.
-
C.
IFC
IFC is an American cable television channel known for airing offbeat comedies, cult films, and independent programming.
-
D.
IFC
IFC (Interface Clear) is a dedicated control line in the IEEE 488 (GPIB) interface used to reset and clear connected devices on the bus.
-
E.
FCU
FCU is the commonly used abbreviation for FC Ulaanbaatar, a professional football club based in Mongolia’s capital city.
- 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_69ca84e0dd1881909800765d1e21f735 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3268fcc8190b7a028f224512e5f |
completed | April 2, 2026, 12:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1e41e1b8081908ef5bb31c27c5264 |
completed | April 5, 2026, 4:25 a.m. |
Created at: March 30, 2026, 8:32 p.m.