Triple
T37208845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Welby |
E922244
|
entity |
| Predicate | rentsBillboardsTo |
P187539
|
FINISHED |
| Object | Mildred Hayes |
—
|
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: Mildred Hayes | Statement: [Red Welby, rentsBillboardsTo, Mildred Hayes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rentsBillboardsTo Context triple: [Red Welby, rentsBillboardsTo, Mildred Hayes]
-
A.
hasSignageIn
Indicates that appropriate signs or signage for an entity are present or installed within a specified location or area.
-
B.
hasSignage
Indicates that appropriate signs or visual markers are present to convey information, directions, warnings, or identification related to the associated entity.
-
C.
hasSignageType
Indicates the specific category or kind of signage associated with an object, location, or entity.
-
D.
usedAsSignage
Indicates that something is employed as a sign or display to convey information, directions, warnings, or identification.
-
E.
sponsorPlacement
Indicates that one entity financially supports or endorses another entity in exchange for a specified form of promotional placement.
- 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_69f76ea4849481909b4a3073efb0114c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb55dc36d08190a0634fa680e13114 |
completed | May 6, 2026, 2:53 p.m. |
Created at: May 3, 2026, 4:15 p.m.