Triple
T36552754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikey Walsh |
E901312
|
entity |
| Predicate | homeThreat |
P186194
|
FINISHED |
| Object | country club development |
—
|
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: country club development | Statement: [Mikey Walsh, homeThreat, country club development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeThreat Context triple: [Mikey Walsh, homeThreat, country club development]
-
A.
globalThreats
Indicates a relationship where certain entities pose or are associated with dangers or risks that have worldwide or cross-border impact.
-
B.
targetsThreat
Indicates that one entity is directing an action or focus specifically toward a perceived threat.
-
C.
laterThreat
Indicates that one entity poses a threat to another at a time subsequent to some referenced or initial point.
-
D.
hasThreats
Indicates that one entity poses or is associated with potential danger, harm, or adverse consequences toward another entity.
-
E.
featuresThreat
Indicates that one entity includes, presents, or contains a threat associated with 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7cabacc1481909e839454ce1057f7 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7c9f4c7c48190ba918d8d5dc8dfd9 |
completed | May 3, 2026, 10:19 p.m. |
Created at: May 3, 2026, 4:11 p.m.