Triple
T30856382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consolidated XP4Y Corregidor |
E785931
|
entity |
| Predicate | developmentCancelled |
P7625
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Consolidated XP4Y Corregidor, developmentCancelled, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentCancelled Context triple: [Consolidated XP4Y Corregidor, developmentCancelled, yes]
-
A.
developmentPhaseAtCancellation
Indicates the specific stage of development a project or product had reached at the time it was cancelled.
-
B.
developmentEnded
Indicates that the process of creating, improving, or expanding something has been completed and no further development is taking place.
-
C.
cancellation
chosen
Indicates that a previously planned or scheduled event, action, or agreement is being annulled, terminated, or rendered no longer valid.
-
D.
constructionProgressAtCancellation
Indicates the level or stage of construction that had been reached at the time the project or contract was cancelled.
-
E.
developmentResult
Indicates that one entity is the outcome, product, or consequence resulting from the development process of 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_69f224b91c14819084e764832fe67a57 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 29, 2026, 8:46 p.m.