Triple
T23737559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bell numbers |
E586577
|
entity |
| Predicate | B5 |
P153481
|
FINISHED |
| Object | 52 |
—
|
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: 52 | Statement: [Bell numbers, B5, 52]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: B5 Context triple: [Bell numbers, B5, 52]
-
A.
B_5
Indicates a relationship where one entity is associated with or classified under a specific category, group, or type represented by the other entity.
-
B.
B2
Indicates a secondary or alternative relationship between two entities, often representing a variant, backup, or subordinate connection to a primary relation.
-
C.
B_4
Indicates a specific type of relationship or interaction labeled as "B_4" between entities, whose exact nature depends on the domain-specific definition of this predicate.
-
D.
B0
Indicates that one entity is the primary or baseline reference point (e.g., default, initial, or base state) in relation to another entity.
-
E.
B_2
Indicates a secondary or alternative type of binary relationship between two entities, often used as a variant or refinement of a primary relation B.
- F. None of above. chosen
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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad356c88190ae29ce403145ee73 |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:11 p.m.