Triple
T2059430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FE Civil |
E45752
|
entity |
| Predicate | resultDelivery |
P9674
|
FINISHED |
| Object | online through NCEES account |
—
|
LITERAL 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: online through NCEES account | Statement: [FE Civil, resultDelivery, online through NCEES account]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultDelivery Context triple: [FE Civil, resultDelivery, online through NCEES account]
-
A.
deliveryConfirmation
Indicates that a delivery has been successfully completed and acknowledged, confirming that the intended recipient has received the item or shipment.
-
B.
deliveredAs
chosen
Indicates that something is provided, transmitted, or presented in a particular form, manner, or role.
-
C.
delivered
Indicates that something has been brought or transported to a recipient or destination, typically completing a transfer or fulfillment of an order, message, or service.
-
D.
delivers
Indicates that one entity transports or hands over something to another entity as intended or required.
-
E.
result
Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
- F. None of above.
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_69a8891a19508190a12ef1e192308dcb |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9af42988190a4e977154dd10312 |
completed | March 7, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_69abb7ad5a7c8190b92575d6053b3fb7 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:40 p.m.