Triple
T36480302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saraya |
E898794
|
entity |
| Predicate | signedWithAEW |
P185567
|
FINISHED |
| Object | 2022 |
—
|
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: 2022 | Statement: [Saraya, signedWithAEW, 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signedWithAEW Context triple: [Saraya, signedWithAEW, 2022]
-
A.
signedAs
Indicates that an entity has signed or endorsed something using a particular name, role, or identity.
-
B.
wasSignedAs
Indicates that an entity formally entered into or agreed to a contract, document, or role under a specified name, status, or terms.
-
C.
signedAfter
Indicates that one signing event occurred later in time than another signing event.
-
D.
agencySignedWith
Indicates that a formal agreement or contract has been established between an agency and another party.
-
E.
alsoSignedWith
Indicates that an entity signed or endorsed something together with another specified entity, as part of the same signing action or agreement.
- F. None of above. chosen
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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be9b9ab481908328e0e8d8ac73d4 |
completed | May 3, 2026, 9:31 p.m. |
Created at: May 3, 2026, 4:10 p.m.