Triple
T3657105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Chat Noir posters |
E77557
|
entity |
| Predicate | reproducedAs |
P5482
|
FINISHED |
| Object | tourist souvenir |
—
|
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: tourist souvenir | Statement: [Le Chat Noir posters, reproducedAs, tourist souvenir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reproducedAs Context triple: [Le Chat Noir posters, reproducedAs, tourist souvenir]
-
A.
reconstructedAs
Indicates that one entity has been rebuilt, recreated, or inferred based on evidence, models, or partial information from another entity.
-
B.
laterRepublishedWith
Indicates that an existing work was republished at a later time in a modified or updated form specified by the related entity.
-
C.
reconstructedIn
Indicates that something has been rebuilt, restored, or re-created within a particular context, location, or medium.
-
D.
circulatedAs
chosen
Indicates that something was distributed, shared, or passed around in the form or role specified by the related entity.
-
E.
laterRepurposedFor
Indicates that something was originally used for one purpose and subsequently assigned a different, new purpose.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3d36c1c8190920397a75de4c47d |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb84650148190bf79231105e58d7f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.