Triple
T33041869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worboys-style road signs |
E845487
|
entity |
| Predicate | mandatorySignShape |
P74189
|
FINISHED |
| Object | blue-filled circle |
—
|
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: blue-filled circle | Statement: [Worboys-style road signs, mandatorySignShape, blue-filled circle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mandatorySignShape Context triple: [Worboys-style road signs, mandatorySignShape, blue-filled circle]
-
A.
signType
chosen
Indicates the specific category or kind of sign involved in the relationship or action.
-
B.
hasSign
Indicates that an entity possesses, displays, or is associated with a particular sign or symbol.
-
C.
signPattern
Indicates a specific arrangement or sequence of positive, negative, or zero signs associated with a set of values or components.
-
D.
signCanBe
Indicates that one sign is capable of serving as, or functioning in the role of, another specified sign.
-
E.
haveSigned
Indicates that an entity has completed and formally agreed to a document, contract, or agreement by signing it.
- 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_69f34951348c8190b56746b0a7018182 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:24 a.m.