Triple
T35976314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grez-sur-Loing |
E1040427
|
entity |
| Predicate | hasNotableArtistVisitor |
P10756
|
FINISHED |
| Object | Carl Larsson |
E108557
|
NE 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: Carl Larsson | Statement: [Grez-sur-Loing, hasNotableArtistVisitor, Carl Larsson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableArtistVisitor Context triple: [Grez-sur-Loing, hasNotableArtistVisitor, Carl Larsson]
-
A.
hasNotablePerformer
Indicates that an entity features or is associated with a performer who is particularly prominent, famous, or otherwise noteworthy.
-
B.
hasNotableGuest
chosen
Indicates that an entity has a guest who is distinguished, prominent, or otherwise noteworthy in some significant way.
-
C.
hasNotableClimberVisitor
Indicates that an entity has been visited or used by at least one climber who is considered notable or distinguished in the climbing community.
-
D.
notableArtist
Indicates that the subject is an artist who is widely recognized or distinguished for their work.
-
E.
hasFeaturedArtist
Indicates that an entity (such as a song or track) includes another artist who appears as a featured performer.
- F. None of above.
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_69f76e27758c81909b711cf38a130aaf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38b7145a388190a34a5687392fb4c0 |
completed | June 22, 2026, 4:16 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.