Triple
T35405020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEI |
E1023341
|
entity |
| Predicate | associatedPortal |
P127704
|
FINISHED |
| Object | Integrated Award Environment |
E63727
|
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: Integrated Award Environment | Statement: [UEI, associatedPortal, Integrated Award Environment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedPortal Context triple: [UEI, associatedPortal, Integrated Award Environment]
-
A.
associatedWebsite
chosen
Indicates that one entity has a related or officially connected website represented by the other entity.
-
B.
associatedSiteType
Indicates the type or category of site with which an entity is associated.
-
C.
associatedThrough
Indicates that two entities are connected or related to each other by means of a specified intermediary, context, or linkage.
-
D.
associatedFair
Indicates a relationship where one entity is linked or connected to a particular fair, such as being held at, organized by, or otherwise related to that fair.
-
E.
associatedFort
Indicates that one entity is connected or linked to a particular fort, typically as its related or corresponding fortification.
- F. None of above.
Provenance (4 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_69f76df43ca4819098711ca4370f1bb9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3836ae29d08190bae88797e42bb45f |
completed | June 21, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.