Triple
T31136843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tatum, New Mexico |
E793667
|
entity |
| Predicate | hasLocalBusinesses |
P120871
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tatum, New Mexico, hasLocalBusinesses, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalBusinesses Context triple: [Tatum, New Mexico, hasLocalBusinesses, true]
-
A.
hasBusinesses
Indicates that an entity owns, operates, or is associated with one or more businesses.
-
B.
hasBusinessIn
chosen
Indicates that one entity conducts, operates, or maintains business activities within the jurisdiction, location, or domain of another entity.
-
C.
hasBusiness
Indicates that one entity owns, operates, or is formally associated with a business entity.
-
D.
hasBusinessOperationsIn
Indicates that a business or organization conducts commercial or operational activities within a specified geographic location or jurisdiction.
-
E.
isBusinessOf
Indicates that one entity is the business, commercial concern, or enterprise associated with, owned by, or operated by another entity.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: April 29, 2026, 9:05 p.m.