Triple
T7125332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Penal Code |
E166043
|
entity |
| Predicate | containsSectionOn |
P43838
|
FINISHED |
| Object | murder |
—
|
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: murder | Statement: [Indian Penal Code, containsSectionOn, murder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsSectionOn Context triple: [Indian Penal Code, containsSectionOn, murder]
-
A.
hasSectionOn
chosen
Indicates that one entity (typically a document or resource) contains a dedicated section or part that specifically addresses or discusses another entity or topic.
-
B.
hasSectionIn
Indicates that one entity contains or includes another entity as a section or subdivision within it.
-
C.
isOnSectionOf
Indicates that one entity is located on, or positioned along, a specific segment or subsection of another entity.
-
D.
hasSect
Indicates that an entity includes, contains, or is associated with a particular sect or subgroup within a larger religious, ideological, or organizational context.
-
E.
appliesToSectionOf
Indicates that something is relevant or applicable specifically to a particular section or subsection of a larger whole.
- 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_69c6888350588190870cd552b427a1cd |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e64d99888190a93c1822e19b5457 |
completed | March 27, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c7289881909f3b533c384f9ed4 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:44 p.m.