Triple
T9741388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foursquare |
E236192
|
entity |
| Predicate | hasOfficialBlog |
P90449
|
FINISHED |
| Object | https://enterprise.foursquare.com/blog |
—
|
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: https://enterprise.foursquare.com/blog | Statement: [Foursquare, hasOfficialBlog, https://enterprise.foursquare.com/blog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialBlog Context triple: [Foursquare, hasOfficialBlog, https://enterprise.foursquare.com/blog]
-
A.
hasOfficial
Indicates that an entity is formally associated with, represented by, or served by a designated official or office-holder.
-
B.
hasOfficialInstagram
Indicates that an entity possesses or is associated with an official Instagram account.
-
C.
hasOfficialHashtag
Indicates that an entity is associated with a designated official hashtag used for identification or promotion.
-
D.
isOfficial
Indicates that an entity holds formal, authorized, or government-recognized status in a given context.
-
E.
hasOfficialReporter
Indicates that something (such as a case, decision, or proceeding) is associated with an officially designated reporter or publication that records it.
- 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_69ca84d3e24481908a476e2231123cf9 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9f2af3e48190b83a442cd0e84062 |
completed | April 1, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69cd03cc128c81908b84ef224f858b4e |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd06aa8bc88190904be19c8953def8 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:23 p.m.