Triple
T13520674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Air Express |
E322884
|
entity |
| Predicate | mailContract |
P45125
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Western Air Express, mailContract, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mailContract Context triple: [Western Air Express, mailContract, yes]
-
A.
mailContractWith
chosen
Indicates that one party sends or delivers a contract to another party via mail as part of a transactional or formal process.
-
B.
emailSupport
Indicates that one entity provides assistance or help to another via email communication.
-
C.
mailedTo
Indicates that something was sent or delivered by mail from one entity to another as the recipient.
-
D.
contactWith
Indicates that two entities are in direct or indirect physical or communicative interaction or touch with each other.
-
E.
addresseeOf
Indicates that one entity is the intended recipient or target audience of a communication, message, or expression from another entity.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafa3df0c8190804174695587f0ea |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:44 p.m.