Triple
T3393174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pennsylvania Constitution |
E71464
|
entity |
| Predicate | currentVersionDate |
P9407
|
FINISHED |
| Object | 1968 |
—
|
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: 1968 | Statement: [Pennsylvania Constitution, currentVersionDate, 1968]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentVersionDate Context triple: [Pennsylvania Constitution, currentVersionDate, 1968]
-
A.
latestVersion
Indicates that one entity is the most recent or up-to-date version of another entity within a sequence or set of versions.
-
B.
latestReleaseDate
chosen
Indicates the date on which the most recent version or release of an entity became available.
-
C.
currentVersionAdopted
Indicates that a specified version is the one presently in use or officially adopted by the relevant entity or system.
-
D.
latestMinorVersion
Indicates that one version is the most recent minor (non-major) update within the series of versions derived from another version.
-
E.
currentVersionDefinedIn
Indicates that the current or active version of an entity is specified or established within a particular source, document, or context.
- 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb851e57c8190983cadcedc58db50 |
completed | March 8, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69adadf705608190975423779430cc58 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:14 p.m.