Triple
T31619944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greendykes |
E806864
|
entity |
| Predicate | hasPostWarOrigin |
P53767
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Greendykes, hasPostWarOrigin, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostWarOrigin Context triple: [Greendykes, hasPostWarOrigin, true]
-
A.
preWarOrigin
Indicates that an entity’s origin, creation, or initial state occurred before a specified war or conflict.
-
B.
postWorldWarIIOrigin
chosen
Indicates that the entity originated, was created, or came into existence after the end of World War II.
-
C.
hasPostWarIssues
Indicates that an entity experiences problems, challenges, or complications that arise in the period following a war or major conflict.
-
D.
postWarHistory
Indicates a relationship where something concerns, describes, or belongs to the historical period and events following a specific war.
-
E.
hasWorldWarIIAssociation
Indicates that there is a notable connection or relevance between an entity and World War II, such as involvement, impact, or contextual association.
- 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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe6fea4a288190bf8615c5d6bf41b4 |
completed | May 8, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69fe6f774de08190975a2393b9a1fd22 |
completed | May 8, 2026, 11:19 p.m. |
Created at: April 30, 2026, 10:40 p.m.