Triple
T28395272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union of Hadiach |
E719268
|
entity |
| Predicate | memberProposed |
P168577
|
FINISHED |
| Object | Kingdom of Poland |
—
|
NE NERFINISHED |
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: Kingdom of Poland | Statement: [Union of Hadiach, memberProposed, Kingdom of Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberProposed Context triple: [Union of Hadiach, memberProposed, Kingdom of Poland]
-
A.
proposedMember
chosen
Indicates that one entity has been suggested or nominated to become a member of another entity or group, but is not yet confirmed as a member.
-
B.
hasProposed
Indicates that one entity has formally suggested or put forward something (such as an idea, plan, or offer) to another entity for consideration or acceptance.
-
C.
isProposed
Indicates that an entity has been formally suggested or put forward for consideration, approval, or adoption.
-
D.
wereProposedBy
Indicates that one or more entities (such as ideas, plans, or items) were put forward or suggested by a specific agent or source.
-
E.
coProposedBy
Indicates that a proposal, idea, or item is jointly put forward or suggested by multiple entities together.
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 28, 2026, 1:16 a.m.