Triple
T28420758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RCW Title 1 |
E719933
|
entity |
| Predicate | isCodifiedAs |
P775
|
FINISHED |
| Object | Title 1 RCW |
—
|
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: Title 1 RCW | Statement: [RCW Title 1, isCodifiedAs, Title 1 RCW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCodifiedAs Context triple: [RCW Title 1, isCodifiedAs, Title 1 RCW]
-
A.
isCodifiedFormOf
Indicates that one entity is the formal, standardized, or officially documented version or expression of another entity.
-
B.
codifiedIn
chosen
Indicates that something is formally recorded, defined, or established within a specific document, code, or legal/institutional text.
-
C.
codifiedUnderAuthority
Indicates that something has been formally established, defined, or recorded according to the rules or power of a specific authority.
-
D.
codifiedThrough
Indicates that something is formally established, expressed, or made authoritative by means of a specific codification process, document, or legal/institutional mechanism.
-
E.
estCodifiéPar
Indicates that something is governed, defined, or regulated by a specific code or codified set of rules.
- 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_69eff6f1c5088190bc24bfbf92f9c017 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:33 a.m.