Triple
T23873909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana Constitution Article 1 Section 24 |
E592809
|
entity |
| Predicate | hasTextFeature |
P62426
|
FINISHED |
| Object | prohibition on ex post facto laws |
—
|
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: prohibition on ex post facto laws | Statement: [Indiana Constitution Article 1 Section 24, hasTextFeature, prohibition on ex post facto laws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTextFeature Context triple: [Indiana Constitution Article 1 Section 24, hasTextFeature, prohibition on ex post facto laws]
-
A.
hasText
Indicates that an entity is associated with or contains a specific piece of textual content.
-
B.
hasTextualCharacter
Indicates that something possesses or exhibits the qualities of written or printed text, such as letters, symbols, or characters.
-
C.
hasTextFrom
Indicates that one entity contains, is derived from, or directly uses the textual content originating from another entity.
-
D.
hasTextBy
Indicates that one entity (such as a document, work, or record) contains or is associated with text authored or written by another entity.
-
E.
hasTextElement
chosen
Indicates that an entity contains or is associated with a specific text-based component or segment.
- 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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cbff91788190b7aabe285014b873 |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:14 p.m.