Triple
T38384855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naardermeer |
E899549
|
entity |
| Predicate | protectionStarted |
P106628
|
FINISHED |
| Object | early 20th century |
—
|
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 20th century | Statement: [Naardermeer, protectionStarted, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectionStarted Context triple: [Naardermeer, protectionStarted, early 20th century]
-
A.
addsProtectionFor
Indicates that one entity provides or increases protective measures or safeguards for another entity.
-
B.
previousProtectionEstablished
chosen
Indicates that a protective measure or status had already been put in place prior to the current point in time or event.
-
C.
laterProtects
Indicates that one entity provides protection for another entity at a later point in time than some referenced event or protection.
-
D.
providesProtectionIn
Indicates that one entity offers protection or safeguarding to another entity within a specified context, location, or situation.
-
E.
protectionType
Indicates the kind or method of protection that is applied to or associated with an 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_69f76e5c9b808190b486523f5c2f817d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.