Triple
T37903649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spanish New Jersey |
E945486
|
entity |
| Predicate | hasClaimStatus |
P84014
|
FINISHED |
| Object | not attested in mainstream historical scholarship |
—
|
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: not attested in mainstream historical scholarship | Statement: [Spanish New Jersey, hasClaimStatus, not attested in mainstream historical scholarship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClaimStatus Context triple: [Spanish New Jersey, hasClaimStatus, not attested in mainstream historical scholarship]
-
A.
hasClaimOn
Indicates that one entity holds a right, entitlement, or demand over another entity or its resources.
-
B.
hasClaimed
Indicates that an entity has asserted ownership, responsibility, or a right over another entity or resource.
-
C.
statusOfClaim
chosen
Indicates the current state or condition of a specific claim within a process or system.
-
D.
hasClaimService
Indicates that an entity provides, manages, or is responsible for a service related to handling claims for another entity.
-
E.
claimedStatusOf
Indicates that one entity asserts or declares a particular status or condition about another entity (often itself).
- 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_69f76ef20bb0819088b5b6ceecb0b8fc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: May 3, 2026, 4:20 p.m.