Triple
T25744373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NY 907L |
E648305
|
entity |
| Predicate | signedStatus |
P159498
|
FINISHED |
| Object | unsigned |
—
|
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: unsigned | Statement: [NY 907L, signedStatus, unsigned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signedStatus Context triple: [NY 907L, signedStatus, unsigned]
-
A.
signedOrAccepted
Indicates that one party has formally agreed to or endorsed something, either by providing a signature or by giving an equivalent form of acceptance.
-
B.
signedAfter
Indicates that one signing event occurred later in time than another signing event.
-
C.
signedDuring
Indicates that an agreement, document, or contract was signed within a specified time period or during a particular event.
-
D.
signedFor
Indicates that one entity formally accepted or acknowledged receipt of something on behalf of another, typically by providing a signature.
-
E.
signedAs
Indicates that an entity has signed or endorsed something using a particular name, role, or identity.
- 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fd1d64c081909bcb839fdfd297d0 |
completed | May 2, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 22, 2026, 3:49 a.m.