Triple
T24686580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taylor, Arizona |
E611310
|
entity |
| Predicate | sharesLocalRegionWith |
P117178
|
FINISHED |
| Object | Snowflake, Arizona |
—
|
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: Snowflake, Arizona | Statement: [Taylor, Arizona, sharesLocalRegionWith, Snowflake, Arizona]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesLocalRegionWith Context triple: [Taylor, Arizona, sharesLocalRegionWith, Snowflake, Arizona]
-
A.
shareRegionalIdentityWith
chosen
Indicates that two entities are perceived to belong to or identify with the same geographic, cultural, or regional community.
-
B.
sharesAreaWith
Indicates that two entities occupy or overlap the same geographic or spatial area.
-
C.
sharesDomainWith
Indicates that two entities operate within, belong to, or are associated with the same domain or domain-like scope.
-
D.
sharesFieldWith
Indicates that two entities are involved in or associated with the same field, discipline, or area of specialization.
-
E.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
- 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_69e2c4d678b081908910f4271627a31a |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 3:18 a.m.