Triple
T18410087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louvre Pyramid courtyard |
E441732
|
entity |
| Predicate | designedAround |
P20207
|
FINISHED |
| Object | Louvre Pyramid entrance scheme |
—
|
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: Louvre Pyramid entrance scheme | Statement: [Louvre Pyramid courtyard, designedAround, Louvre Pyramid entrance scheme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedAround Context triple: [Louvre Pyramid courtyard, designedAround, Louvre Pyramid entrance scheme]
-
A.
developedAround
chosen
Indicates that one entity was created, designed, or evolved with the other entity as its central focus, basis, or surrounding context.
-
B.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
-
C.
designedApproximately
Indicates that one entity was created, planned, or engineered to an estimated or imprecise degree in relation to another entity or specification.
-
D.
formsAround
Indicates that one entity develops or shapes itself so as to encircle, surround, or be organized around another entity.
-
E.
designedFeature
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
- 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e5195b98808190b9cfb2e444f2b524 |
completed | April 19, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 10:47 a.m.