Triple
T33564531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mkhitar Gosh |
E859718
|
entity |
| Predicate | legalTextAuthored |
P134288
|
FINISHED |
| Object | Armenian civil and canon law code |
—
|
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: Armenian civil and canon law code | Statement: [Mkhitar Gosh, legalTextAuthored, Armenian civil and canon law code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalTextAuthored Context triple: [Mkhitar Gosh, legalTextAuthored, Armenian civil and canon law code]
-
A.
legalContent
Indicates that the associated material complies with applicable laws and regulations and is permitted for use, distribution, or display.
-
B.
legalElement
Indicates that something is a constituent part or component required or recognized within a legal framework, rule, or process.
-
C.
lawWritten
chosen
Indicates that a specific law has been authored, drafted, or formally written by a particular entity.
-
D.
legalTextTypeWorkedOn
Indicates that an entity has worked on or handled a specific type or category of legal text.
-
E.
legalAuthorityIn
Indicates that an entity holds official legal power, jurisdiction, or governing authority within a specified area or domain.
- 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff27b125948190aced0fe0189fd39a |
completed | May 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69ff26c30a0481909ef6a54ded851e42 |
completed | May 9, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:40 a.m.