Triple
T38114467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J’adore Absolu |
E951752
|
entity |
| Predicate | notableNote |
—
|
GENERATED |
| Object | jasmine |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableNote Context triple: [J’adore Absolu, notableNote, jasmine]
-
A.
notableBoard
Indicates that an entity serves on, or is significantly associated with, a board that is notable or of particular importance.
-
B.
notableSave
Indicates that an entity is recognized for having made a particularly significant or memorable save (e.g., in a game, match, or critical situation).
-
C.
isNotedOn
Indicates that information about one entity is recorded, mentioned, or annotated on another entity (such as a document, record, or medium).
-
D.
notedIn
Indicates that information about one entity is mentioned, recorded, or referenced within another entity, such as a document, record, or source.
-
E.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
- F. None of above. chosen
Provenance (1 batch)
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_69f76f07734c8190814e937e12257a78 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.