Triple
T14457428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poland (seniorate system) |
E358491
|
entity |
| Predicate | languageOfLegalActs |
P27218
|
FINISHED |
| Object | Latin |
—
|
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: Latin | Statement: [Poland (seniorate system), languageOfLegalActs, Latin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfLegalActs Context triple: [Poland (seniorate system), languageOfLegalActs, Latin]
-
A.
languageOfLegalCode
Indicates that a specified language is the language in which a particular legal code or body of law is written or officially expressed.
-
B.
languageOfPromulgation
chosen
Indicates the language in which a law, decree, or official act is formally issued or proclaimed.
-
C.
languageOfJurisdiction
Indicates the language officially used for legal and administrative purposes within a given jurisdiction.
-
D.
languageOfOriginalPromulgation
Indicates the language in which a law, regulation, or official text was originally formally issued or published.
-
E.
hasLanguageLegislation
Indicates that there exists formal legislation or legal provisions governing the use, status, or regulation of language in relation to the subject entity.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91a9c0d48190ae015e5e0db806ca |
completed | April 14, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.