Triple
T25744375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NY 907L |
E648305
|
entity |
| Predicate | publicSigning |
P171388
|
FINISHED |
| Object | not signed as a public highway |
—
|
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: not signed as a public highway | Statement: [NY 907L, publicSigning, not signed as a public highway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicSigning Context triple: [NY 907L, publicSigning, not signed as a public highway]
-
A.
typicallySignedWith
Indicates that an entity is most commonly or customarily accompanied by a particular signature, mark, or signing method.
-
B.
coSignedWith
Indicates that an entity has jointly signed a document, agreement, or obligation together with another entity.
-
C.
canSign
Indicates that an entity has the authority or capability to sign a document, agreement, or similar item.
-
D.
signingProcedure
Indicates the formal process or method by which an agreement, document, or contract is signed or executed between parties.
-
E.
hasSignFor
Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about another entity.
- 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_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 22, 2026, 3:49 a.m.