Triple
T23796311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louvre-Lens |
E588549
|
entity |
| Predicate | collectionSource |
P10914
|
FINISHED |
| Object | Musée du Louvre in Paris |
—
|
NE NERFINISHED |
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: Musée du Louvre in Paris | Statement: [Louvre-Lens, collectionSource, Musée du Louvre in Paris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectionSource Context triple: [Louvre-Lens, collectionSource, Musée du Louvre in Paris]
-
A.
collectionOrigin
chosen
Indicates that one entity is the source, provenance, or originating context from which a collection of items or data has been derived or assembled.
-
B.
collectionRepository
Indicates a relationship where a repository is responsible for storing, managing, or providing access to a collection.
-
C.
collectionBy
Indicates that one entity is the collector or curator responsible for assembling, managing, or owning a particular collection of items represented by another entity.
-
D.
collectionScope
Indicates the extent, boundaries, or range over which a collection (such as a set of items, data, or resources) is defined or intended to apply.
-
E.
collectionModel
Indicates that one entity serves as a model, template, or representative example for a collection of related entities.
- 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_69e25d15db58819092ac1e6791696fd9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c6dc94d481908800385a58d2c452 |
completed | April 29, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:48 p.m.