Triple
T11825823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Code of Civil Procedure 1859 |
E281257
|
entity |
| Predicate | languageOfDraft |
P2245
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Code of Civil Procedure 1859, languageOfDraft, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfDraft Context triple: [Code of Civil Procedure 1859, languageOfDraft, English]
-
A.
draftedInLanguage
chosen
Indicates that a document, text, or content was originally written or composed using a specific natural language.
-
B.
languageOfWritings
Indicates that a specified language is the one in which certain writings or written works are composed.
-
C.
languageOfUnderlyingWork
Indicates the language in which the original or underlying work (from which a derived or related work stems) is expressed.
-
D.
languageOfIssue
Indicates the language in which a particular item, document, or resource is issued or published.
-
E.
contentLanguage
Indicates the language in which the content is expressed or intended to be understood.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5eb299481909de3c0e85628fbe4 |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.