Triple
T38114397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corolle collection |
E951750
|
entity |
| Predicate | hasNotableLook |
P200117
|
FINISHED |
| Object | Bar suit |
E951751
|
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: Bar suit | Statement: [Corolle collection, hasNotableLook, Bar suit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableLook Context triple: [Corolle collection, hasNotableLook, Bar suit]
-
A.
hasNotableFeature
Indicates that an entity possesses a specific characteristic, trait, or attribute that is considered significant or noteworthy.
-
B.
hasNotableHead
Indicates that an entity is associated with a particularly prominent or distinguished leader or chief figure.
-
C.
hasNotableImpressionOf
Indicates that one entity holds a particularly strong, memorable, or significant impression of another entity.
-
D.
hasParticularNotableCharacteristic
Indicates that an entity possesses a specific, noteworthy characteristic or quality that distinguishes it in some relevant context.
-
E.
notableAppearanceFeature
chosen
Indicates that an entity is characterized by a distinctive or noteworthy physical appearance trait.
- 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_69f76f07734c8190814e937e12257a78 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41681bcb1c819080c0d01847dbf71a |
completed | June 28, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.