Triple
T17141690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pulqui II |
E415979
|
entity |
| Predicate | developmentEndPeriod |
P73439
|
FINISHED |
| Object | early 1950s |
—
|
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: early 1950s | Statement: [Pulqui II, developmentEndPeriod, early 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentEndPeriod Context triple: [Pulqui II, developmentEndPeriod, early 1950s]
-
A.
developmentEnded
chosen
Indicates that the process of creating, improving, or expanding something has been completed and no further development is taking place.
-
B.
buildPeriodEnd
Indicates the point in time at which a construction or building phase is considered completed.
-
C.
developmentBegan
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
-
D.
endOfExtensionPeriod
Indicates that a previously granted extension has reached or passed its final allowable time limit.
-
E.
deploymentEnd
Indicates the point in time or event at which a deployment process or deployment state comes to an end.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f2d5de10819090cbd65661b018d3 |
completed | April 18, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.