Triple
T31190989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercy For Animals |
E795178
|
entity |
| Predicate | hasTaxID |
P34548
|
FINISHED |
| Object | 54-2076145 |
—
|
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: 54-2076145 | Statement: [Mercy For Animals, hasTaxID, 54-2076145]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTaxID Context triple: [Mercy For Animals, hasTaxID, 54-2076145]
-
A.
requiresTaxpayerIdentification
chosen
Indicates that providing a taxpayer identification number or equivalent tax-related identifier is necessary for the related entity, transaction, or process.
-
B.
taxId
Indicates that an entity is associated with a specific taxonomic identifier used to uniquely reference its position in a taxonomic classification system.
-
C.
hasIdentityDocument
Indicates that an entity possesses or is associated with a specific identity document.
-
D.
hasOwnTaxSystem
Indicates that an entity maintains and administers its own distinct system of taxation, separate from other jurisdictions or authorities.
-
E.
hasCorporateTaxStatus
Indicates that an entity has a specific classification or condition regarding its obligation to pay corporate taxes.
- 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_69f224d7a6a481908187c4362a8a525f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 29, 2026, 9:08 p.m.