Triple
T2131973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PKWN |
E46560
|
entity |
| Predicate | claimedLegitimacyFrom |
P19049
|
FINISHED |
| Object | Polish people |
—
|
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: Polish people | Statement: [PKWN, claimedLegitimacyFrom, Polish people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedLegitimacyFrom Context triple: [PKWN, claimedLegitimacyFrom, Polish people]
-
A.
legitimizedBy
Indicates that something gains legal, formal, or social validity as a result of the authority, action, or endorsement of another entity.
-
B.
legalAuthorityClaimedBy
Indicates that one party asserts or claims to possess legal authority, power, or jurisdiction over another party or matter.
-
C.
claimedAs
Indicates that one entity asserts ownership, authorship, responsibility, or some other form of association over another entity.
-
D.
helpedLegitimize
chosen
Indicates that one entity’s actions or support contributed to making another entity appear more credible, acceptable, or officially recognized.
-
E.
claimsToBe
Indicates that one entity asserts or declares itself to have a particular identity, role, or property, regardless of whether this assertion is true.
- 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_69a88a1626548190ae59a5028c3baa8e |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbb7b13ac819094d43159fff984cf |
completed | March 7, 2026, 5:45 a.m. |
| PD | Predicate disambiguation | batch_69abb7bf56e481909b0f497d238451cc |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.