Triple
T37965510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King's Highway (Ontario) |
E947129
|
entity |
| Predicate | historicallySignedAs |
P203702
|
FINISHED |
| Object | King's Highway |
E547581
|
NE 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: King's Highway | Statement: [King's Highway (Ontario), historicallySignedAs, King's Highway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallySignedAs Context triple: [King's Highway (Ontario), historicallySignedAs, King's Highway]
-
A.
wasSignedAs
Indicates that an entity formally entered into or agreed to a contract, document, or role under a specified name, status, or terms.
-
B.
alsoSignedAs
Indicates that an entity is additionally known to have signed or endorsed something under another name or identity.
-
C.
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.
-
D.
signedAs
Indicates that an entity has signed or endorsed something using a particular name, role, or identity.
-
E.
agreementSignedBy
Indicates that a particular agreement has been formally signed or executed by a specified party.
- F. None of above. chosen
Provenance (5 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a01ca0db6f08190bed479584114e63d |
completed | May 11, 2026, 12:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a412caa5e848190a2db41496dbeed42 |
completed | June 28, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_6a01c96ff4a08190a4fbf0cebbda95b4 |
completed | May 11, 2026, 12:20 p.m. |
| PDg | Predicate description generation | batch_6a01ca0bf57881908d0dcfb2a25556b3 |
completed | May 11, 2026, 12:22 p.m. |
Created at: May 3, 2026, 4:20 p.m.