Triple
T2031296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adele Astaire |
E44521
|
entity |
| Predicate | knownForCharacteristic |
P662
|
FINISHED |
| Object | wit |
—
|
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: wit | Statement: [Adele Astaire, knownForCharacteristic, wit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForCharacteristic Context triple: [Adele Astaire, knownForCharacteristic, wit]
-
A.
characterizedBy
chosen
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
B.
recognizedFor
Indicates that one entity is acknowledged, credited, or honored for a particular achievement, quality, contribution, or work associated with another entity.
-
C.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
D.
recognizedAs
Indicates that one entity is acknowledged or accepted as having the identity, role, status, or classification of another entity.
-
E.
knownFrom
Indicates that one entity is aware of, has learned about, or recognizes another entity through a specified source, context, or medium.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb915c9548190809d08c4d67466fb |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a656248190ac2ced196b35bc6b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.