Triple
T27782578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyon Estates |
E699371
|
entity |
| Predicate | streetSignText |
P20223
|
FINISHED |
| Object | Lyon Estates |
—
|
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: Lyon Estates | Statement: [Lyon Estates, streetSignText, Lyon Estates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetSignText Context triple: [Lyon Estates, streetSignText, Lyon Estates]
-
A.
hasSignageName
chosen
Indicates that an entity has a specific name or label as it appears on its physical signage.
-
B.
roadSignPrefix
Indicates a relationship where one element serves as the initial or leading part of a road sign’s text, code, or designation.
-
C.
roadSignageIndicates
Indicates that a piece of road signage conveys, displays, or communicates specific information, instructions, or warnings about road conditions or regulations.
-
D.
signpostFeature
Indicates that one entity serves as a signpost-related feature or element associated with another entity.
-
E.
hasSignageIn
Indicates that appropriate signs or signage for an entity are present or installed within a specified location or area.
- F. None of above.
Provenance (3 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 5:11 p.m.