Triple
T14067476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siebenbürger Sachsen |
E338511
|
entity |
| Predicate | legalFoundationPeriod |
P112686
|
FINISHED |
| Object | 13th century |
—
|
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: 13th century | Statement: [Siebenbürger Sachsen, legalFoundationPeriod, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalFoundationPeriod Context triple: [Siebenbürger Sachsen, legalFoundationPeriod, 13th century]
-
A.
foundationInLaw
Indicates that something is based on, justified by, or derives its authority from a specific law or legal framework.
-
B.
legalBasis
Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
-
C.
legalPredecessorFoundedIn
Indicates that one legal predecessor entity was founded or established in a specified time or place.
-
D.
legalStatusOfFoundation
Indicates the legal status or standing that a foundation holds under applicable laws or regulations.
-
E.
legalBackground
Indicates that an entity has education, training, or experience related to law or the legal profession.
- F. None of above. chosen
Provenance (4 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de568b81f08190a571004261c0e8e4 |
completed | April 14, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:21 p.m.