Triple
T1395147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tribonian |
E30647
|
entity |
| Predicate | legalTextTypeWorkedOn |
P27701
|
FINISHED |
| Object | imperial constitutions |
—
|
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: imperial constitutions | Statement: [Tribonian, legalTextTypeWorkedOn, imperial constitutions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalTextTypeWorkedOn Context triple: [Tribonian, legalTextTypeWorkedOn, imperial constitutions]
-
A.
legalCodeType
Indicates the specific category or classification of a legal code that applies to an entity or situation.
-
B.
legalSystemWorkedOn
Indicates that a legal system has been applied to, influenced, or modified by some agent or process.
-
C.
legalCitationType
Indicates the specific kind or category of legal citation that characterizes the relationship between the citing and cited legal sources.
-
D.
legalForm
Indicates the specific legal structure or organizational type under which an entity is formally constituted and recognized by law.
-
E.
legalRepresentation
Indicates that one entity formally acts on behalf of another in legal matters, such as providing counsel, advocacy, or defense within a legal system.
- 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c37e60388190a8efcb345be7a1b9 |
completed | March 1, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69a4bf017f8081908572121560ec621f |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c13270d8819081d8ee1be34cabf5 |
completed | March 1, 2026, 10:44 p.m. |
Created at: March 1, 2026, 7:59 p.m.