Triple

T26118608
Position Surface form Disambiguated ID Type / Status
Subject Faculty of Engineering and Architecture E658892 entity
Predicate abbreviation P43 FINISHED
Object FEA
FEA is an abbreviation commonly used for the Faculty of Engineering and Architecture at certain universities, denoting an academic unit that offers engineering and architecture programs.
E1712902 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: FEA | Statement: [Faculty of Engineering and Architecture, abbreviation, FEA]
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: FEA
Triple: [Faculty of Engineering and Architecture, abbreviation, FEA]
Generated description
FEA is an abbreviation commonly used for the Faculty of Engineering and Architecture at certain universities, denoting an academic unit that offers engineering and architecture programs.

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_69ee5bc20298819099a42be042eb2349 completed April 26, 2026, 6:38 p.m.
NER Named-entity recognition batch_69f60aca701c819093f82d6059fa0475 completed May 2, 2026, 2:31 p.m.
NED1 Entity disambiguation (via context triple) batch_6a118566c4bc8190b5f16f210d310125 completed May 23, 2026, 10:45 a.m.
NEDg Description generation batch_6a1185fa85a481908ab81328b0e12145 completed May 23, 2026, 10:48 a.m.
NED2 Entity disambiguation (via description) batch_6a11867ada8081908d2c617f22e79325 completed May 23, 2026, 10:50 a.m.
Created at: April 26, 2026, 8:07 p.m.