Triple
T28261957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Périchole |
E712604
|
entity |
| Predicate | revisedVersionActs |
P104500
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [La Périchole, revisedVersionActs, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revisedVersionActs Context triple: [La Périchole, revisedVersionActs, 3]
-
A.
revisedActs
chosen
Indicates that one act is a modified, updated, or corrected version of another act.
-
B.
repealedAndReenacted
Indicates that an existing law or regulation was formally revoked and simultaneously replaced by a new version covering the same subject matter.
-
C.
implementsAct
Indicates that one entity carries out, executes, or puts into effect a specified act, plan, or directive associated with another entity.
-
D.
revisedVersionType
Indicates that one entity is a revised form of another, specifying the type or nature of the revision made.
-
E.
enactedAs
Indicates that one entity has been formally established, implemented, or made legally effective in the specific form represented by another entity.
- 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_69efb5207eb08190827e4c34048030b1 |
completed | April 27, 2026, 7:12 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 27, 2026, 11:12 p.m.