Triple
T36506432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NJ Route 444 |
E899477
|
entity |
| Predicate | notSignedAs |
P185781
|
FINISHED |
| Object | NJ Route 444 |
—
|
NE NERFINISHED |
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: NJ Route 444 | Statement: [NJ Route 444, notSignedAs, NJ Route 444]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notSignedAs Context triple: [NJ Route 444, notSignedAs, NJ Route 444]
-
A.
isSigned
Indicates that an entity has been formally endorsed or authenticated through a signature or signing action.
-
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.
signedAs
Indicates that an entity has signed or endorsed something using a particular name, role, or identity.
-
D.
haveSigned
Indicates that an entity has completed and formally agreed to a document, contract, or agreement by signing it.
-
E.
typicallySignedWith
Indicates that an entity is most commonly or customarily accompanied by a particular signature, mark, or signing method.
- 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_69f76e5b92088190933afda3f7531dd4 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c3705b5c81908c84004543a71c07 |
completed | May 3, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:10 p.m.