Triple
T21792027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edwin Lutyens buildings in Scotland |
E537992
|
entity |
| Predicate | languageOfDesignDocumentation |
P42636
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Edwin Lutyens buildings in Scotland, languageOfDesignDocumentation, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfDesignDocumentation Context triple: [Edwin Lutyens buildings in Scotland, languageOfDesignDocumentation, English]
-
A.
languageOfDocumentation
chosen
Indicates the language in which the documentation for an entity is written or provided.
-
B.
languageDesigned
Indicates that one entity created or developed the language used or associated with another entity.
-
C.
hasDesignLanguage
Indicates that one entity employs, follows, or is characterized by the design language specified by another entity.
-
D.
languageOfInstructions
Indicates that one entity specifies the language in which instructions or guidance are provided for another entity.
-
E.
legalDesignationLanguage
Indicates the language in which a legal designation, status, or title is formally expressed or recorded.
- 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_69e0c47198f881908cb0d237266c10e9 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f06220bbe0819091cf3b41aa788cc3 |
completed | April 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:52 p.m.