Triple
T29312424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | country estate Paradies |
E743273
|
entity |
| Predicate | hasTypeOfGrounds |
P194417
|
FINISHED |
| Object | landscaped estate grounds |
—
|
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: landscaped estate grounds | Statement: [country estate Paradies, hasTypeOfGrounds, landscaped estate grounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfGrounds Context triple: [country estate Paradies, hasTypeOfGrounds, landscaped estate grounds]
-
A.
hasGrounds
Indicates that one entity possesses or includes a physical area of land or outdoor space associated with it.
-
B.
hasTypeOfCourt
Indicates that an entity is associated with or classified by a specific type or category of court.
-
C.
hasTypeOfCase
Indicates that an entity is associated with or classified under a particular type or category of case.
-
D.
opposedOnGroundsOf
Indicates that one party is against or rejects another party, proposal, or action specifically for the stated reasons or justification.
-
E.
hasGround
Indicates that one entity possesses, is supported by, or is associated with a ground or base surface.
- F. None of above. chosen
Provenance (4 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_69f0912502c8819087d9e8398ee991a8 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
| PDg | Predicate description generation | batch_69fd6f9a8bd881909983fe8f4cd0ba98 |
completed | May 8, 2026, 5:07 a.m. |
Created at: April 28, 2026, 1:17 p.m.