Triple
T20393262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Cracow |
E500135
|
entity |
| Predicate | hasAssociatedClaim |
P73422
|
FINISHED |
| Object | claim to the Polish crown |
—
|
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: claim to the Polish crown | Statement: [Duke of Cracow, hasAssociatedClaim, claim to the Polish crown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedClaim Context triple: [Duke of Cracow, hasAssociatedClaim, claim to the Polish crown]
-
A.
hasClaimOn
chosen
Indicates that one entity holds a right, entitlement, or demand over another entity or its resources.
-
B.
attributeClaim
Indicates that one entity asserts or specifies a particular attribute or property about another entity.
-
C.
hasClaimType
Indicates that an entity is associated with or categorized under a specific type of claim.
-
D.
hasKeyClaim
Indicates that one entity contains, presents, or is associated with a central or primary claim expressed by another entity.
-
E.
supportsClaim
Indicates that one entity provides evidence, reasoning, or backing that strengthens or validates the truth or credibility of another entity’s claim.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6791144788190a0ab42cf0141b6a3 |
completed | April 20, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:28 a.m.