Triple
T32844196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungarian customary law |
E840050
|
entity |
| Predicate | partiallyWrittenDownIn |
P184026
|
FINISHED |
| Object | Tripartitum |
—
|
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: Tripartitum | Statement: [Hungarian customary law, partiallyWrittenDownIn, Tripartitum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyWrittenDownIn Context triple: [Hungarian customary law, partiallyWrittenDownIn, Tripartitum]
-
A.
laterWrittenDownIn
Indicates that information, events, or content were recorded or documented at a later time than when they originally occurred or were created.
-
B.
laterWrittenDownAs
Indicates that something was recorded or documented in written form at a subsequent time after its original occurrence or expression.
-
C.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
D.
wroteIn
Indicates that an entity authored or composed something using a particular language, medium, or writing system.
-
E.
firstWrittenDown
Indicates that an instance marks the earliest time or occasion when something was recorded in written form.
- 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_69f3493ff0888190b51e974eae2a7834 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 1, 2026, 1:16 a.m.