Triple
T18796410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Court of Human Rights extension studies |
E459644
|
entity |
| Predicate | designAspect |
P133048
|
FINISHED |
| Object | site planning |
—
|
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: site planning | Statement: [European Court of Human Rights extension studies, designAspect, site planning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designAspect Context triple: [European Court of Human Rights extension studies, designAspect, site planning]
-
A.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
B.
designDescription
Indicates that an entity has a textual explanation or summary of its design, structure, or intended configuration.
-
C.
designOutcome
Indicates the result, effect, or consequence produced by a particular design or design process.
-
D.
designMethod
Indicates that one entity is used as the method, approach, or technique by which another entity is designed or created.
-
E.
designLead
Indicates that one entity serves as the primary designer or person in charge of leading the design work for another entity or project.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a01ed3c08190890d9518ed69fdee |
completed | April 20, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:53 a.m.